CONNECT APP
Build with Trengo
Customer service software
Help Desk & Support
- API key
MCP
Give your agent Trengo tools
Every Trengo action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Trengo account for each tool call — you store no tokens.
// 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()
// e.g. run Assign Ticket:
const result = await mcp.callTool({
name: "trengo-assign-ticket",
arguments: {
ticketId: 10,
type: "Assignment Type",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Assign Ticket:
result = await session.call_tool("trengo-assign-ticket", {
"ticketId": 10,
"type": "Assignment Type",
})API PROXY
Call the Trengo API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Trengo API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://app.trengo.eu/api/v2/users",
})
// Any allowed Trengo endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://app.trengo.eu/api/v2/users
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcHAudHJlbmdvLmV1L2FwaS92Mi91c2Vycw?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Trengo actions from your backend
Connect a user's Trengo account once, then run Assign Ticket on their behalf from your own code — TypeScript, Python, or plain HTTP.
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-assign-ticket",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
trengo: { authProvisionId: "apn_xxxxxxx" },
ticketId: 10,
type: "Assignment Type",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="trengo-assign-ticket",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"trengo": {"authProvisionId": "apn_xxxxxxx"},
"ticketId": 10,
"type": "Assignment Type",
},
)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-assign-ticket",
"configured_props": {
"trengo": { "authProvisionId": "apn_xxxxxxx" },
"ticketId": 10,
"type": "Assignment Type"
}
}'TOOLS
Trengo actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Assign Ticket
actionAssign a Trengo ticket to a user or a team. See the documentationWritev0.0.4 -
Attach Label
actionAttach a label to a ticket. See the documentationWritev0.0.9 -
Close Ticket
actionClose a ticket. See the documentationWritev0.0.7 -
Create Contact
actionCreates a contact. If a contact with given identifier already exists, returns it. See the documentationWritev0.0.15 -
Find Contacts
actionFinds contacts with the given term. See the documentationRead-onlyv0.0.14 -
Get Article
actionGet a specific article. See the documentationRead-onlyv0.0.6 -
Get Block
actionGet a specific block. See the documentationRead-onlyv0.0.6 -
Get Category
actionGet a specific category. See the documentationRead-onlyv0.0.6 -
Get Email Message Content
actionRetrieve the full email content for a specific ticket message. Use this whenemail_message.collapsedis true in the List Messages response. See the documentationRead-onlyv0.0.5 -
Get Help Center
actionGet a specific help center. See the documentationRead-onlyv0.0.6 -
Get Label
actionGet a label by ID. See the documentationRead-onlyv0.0.9 -
Get Message
actionGet a message by ID. See the documentationRead-onlyv0.0.9 -
Get Ticket
actionGet a specific ticket. See the documentationRead-onlyv0.0.5 -
List All Blocks
actionList all blocks in a help center. See the documentationRead-onlyv0.0.6 -
List All Categories
actionList all categories in a help center. See the documentationRead-onlyv0.0.6 -
List All Quick Replies
actionList all quick replies. See the documentationRead-onlyv0.0.6 -
List Articles
actionList articles from a help center according to the specified criteria. See the documentationRead-onlyv0.0.12 -
List Channel ID Options
actionRetrieves available options for the Channel ID field.Read-onlyv0.0.2 -
List Help Center ID Options
actionRetrieves available options for the Help Center ID field.Read-onlyv0.0.2 -
List Help Centers
actionList all help centers. See the documentationRead-onlyv0.0.6 -
List Label ID Options
actionRetrieves available options for the Label ID field.Read-onlyv0.0.2 -
List Labels
actionList all labels. See the documentationRead-onlyv0.0.9 -
List Messages
actionList messages from a ticket. See the documentationRead-onlyv0.0.11 -
List Team ID Options
actionRetrieves available options for the Team ID field.Read-onlyv0.0.2 -
List Ticket ID Options
actionRetrieves available options for the Ticket ID field.Read-onlyv0.0.2 -
List Ticket Result ID Options
actionRetrieves available options for the Ticket Result ID field.Read-onlyv0.0.2 -
List Tickets
actionList tickets according to the specified criteria. See the documentationRead-onlyv0.0.11 -
List To User ID Options
actionRetrieves available options for the To User ID field.Read-onlyv0.0.2 -
Log A Voice Call
actionLogs a phone call from external VOIP applications, See the documentationWritev0.0.14 -
Remove Label
actionRemove a label from a ticket. See the documentationWritev0.0.2 -
Send A Message
actionThis action can be used to easily send a message or an email without having to think about contacts or tickets, See the documentationWritev0.0.15 -
Send A Team Chat Message
actionSend a message as a bot in the Team Chat, See the documentationWritev0.0.14 -
Send A Ticket Media Message
actionSend 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'sAttachment IDs. Example:ticketId=991469294,file=https://example.com/return-label.pdf,caption=Your return labelposts the file to that conversation. See the documentationWritev0.0.1 -
Send A Ticket Message
actionSend a message to a ticket. See the documentationWritev0.0.8 -
Send A WhatsApp Message Template
actionSends a WhatsApp message template, See the documentationWritev0.0.14 -
Upload File
actionUpload a file to attach to an email ticket reply. Returns{ id, size, name, mime }; passidto Send A Ticket Message'sAttachment IDs. Unused uploads are removed automatically, so send the message soon after uploading. For WhatsApp, live chat or social channels, use Send A Ticket Media Message instead. Example:file=https://example.com/return-label.pdfreturns{ "id": 423874896, "size": 13264, "name": "return-label.pdf", "mime": "application/pdf" }. See the documentationWritev0.0.1
-
New Inbound Message Event (Instant)
triggerEmit new event when an inbound message is received. See the documentationInstantv0.0.13 -
New Internal Note Event (Instant)
triggerEmit new event when an internal note is added. See the documentationInstantv0.0.13 -
New Outbound Message Event (Instant)
triggerEmit new event when an outbound message sent. See the documentationInstantv0.0.13 -
New Phone Call Ended Event (Instant)
triggerEmit new event when a phone call ends. See the documentationInstantv0.0.13 -
New Phone Call Missed Event (Instant)
triggerEmit new event when an phone call missed. See the documentationInstantv0.0.13 -
New Phone Call Started Event (Instant)
triggerEmit new event when a phone call starts. See the documentationInstantv0.0.13 -
New Ticket Label Added Event (Instant)
triggerEmit new event when a ticket label is added. See the documentationInstantv0.0.13 -
New Voice Call Recorded Event (Instant)
triggerEmit new event when a voice call is recorded. See the documentationInstantv0.0.12 -
Ticket Closed (Instant)
triggerEmit new event when a ticket is closed. See the documentationInstantv0.0.11 -
Ticket Reopened (Instant)
triggerEmit new event when a ticket is reopened. See the documentationInstantv0.0.11
- App slug
- trengo
- Authentication
- API key
- Categories
- Help Desk & Support
- Actions
- 36
- Triggers
- 10
- API proxy
- Available