View as Markdown
Trengo icon

Trengo ACTION

Send A Ticket Message

Send a message to a ticket. 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 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-message",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    trengo: { authProvisionId: "apn_xxxxxxx" },
    ticketId: 10,
    message: "Message",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Send A Ticket Message inputs
Property Type Description
ticketId Ticket ID integer
Select a ticket or provide an ID
Required Dynamic
message Message string
The message send to the receiver.
Required
internalNote Internal Note boolean
If true, this message will be visible only to your team
Optional
subject Subject string
The subject of the message. Only used when the message is an email.
Optional
attachmentIds Attachement IDs integer[]
IDs of uploaded files. Required if Body not set.
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-message
Version
0.0.7
App
Trengo
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes