Trengo ACTION
Send A Ticket Media Message
Send a file to a ticket on a non-email channel, such as WhatsApp, live chat or social. Use List Tickets to find the ticket ID. Returns an empty response on success. For email tickets, use Upload File and pass the returned ID to Send A Ticket Message's
Attachment IDs. Example: ticketId = 991469294, file = https://example.com/return-label.pdf, caption = Your return label posts the file to that conversation. See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Trengo account once, then configure and run Send A Ticket Media Message from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "trengo-send-a-ticket-media-message",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
trengo: { authProvisionId: "apn_xxxxxxx" },
ticketId: 10,
file: "File Path or URL",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "trengo-send-a-ticket-media-message",
"configured_props": {
"trengo": { "authProvisionId": "apn_xxxxxxx" },
"ticketId": 10,
"file": "File Path or URL"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "trengo",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "trengo-send-a-ticket-media-message",
arguments: {
ticketId: 10,
file: "File Path or URL",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
ticketId Ticket ID | integer | Select a ticket or provide an ID Required Dynamic |
file File Path or URL | string | A file URL or a path to a file in the /tmp directory (e.g. /tmp/label.pdf). Supported types include images, videos, audio, text, PDF and MS Office files (max 20 MB) Required |
caption Caption | string | A caption to send with the file, e.g. Your return label. Not shown on live chat or email tickets. Optional |
syncDir SyncDir | dir | Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- trengo-send-a-ticket-media-message
- Version
- 0.0.1
- App
- Trengo
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗