View as Markdown
Trengo icon

Trengo ACTION

Send A Team Chat Message

Send a message as a bot in the Team Chat, 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 Team Chat 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-team-chat-message",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    trengo: { authProvisionId: "apn_xxxxxxx" },
    threadId: 10,
    toUserId: 10,
  },
})

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 Team Chat Message inputs
Property Type Description
threadId Thread ID integer
Required if To User ID is not set
Optional
toUserId To User ID integer
Required if Thread ID is not set
Optional Dynamic
body Body string
HTML message body. Required if Attachment IDs is not set. URLs will be automatically converted to A-tags.
Optional
attachmentIds Attachement IDs integer[]
IDs of uploaded files. Required if Body not set.
Optional
parentId Parent ID integer
Set the parent message ID to reply to it.
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-team-chat-message
Version
0.0.13
App
Trengo
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes