.DkNUKaKx_ZLAT4m.webp?dpl=dpl_9Hx2VMmiEy3kxDNKf1opN6MSWyX6){kind=small}
Connectors / Customer service · HTTP Connector
Automate Trengo with Tray.ai
Create a ticket, send a ticket message and create a contact in Trengo, and start a workflow when Trengo sends “Inbound message received”.
Thanks — someone from our team will be in touch soon.
What can you do with Trengo on Tray.ai?
Trengo is a shared customer inbox that brings email, WhatsApp, live chat, voice and social messages into one ticketing workspace for support and sales teams. Tray.ai connects to Trengo through the HTTP Connector, so your workflows can call the Trengo API alongside the rest of your stack.
- Connects through
- HTTP Connector
- Authentication
- A bearer token
- Base URL
- https://app.trengo.com/api/v2
What the Trengo API covers
6 resources and 21 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow.
Tickets
- List tickets
- Create a ticket
- Assign a ticket
- Close a ticket
Messages
- Send a ticket message
- List ticket messages
- Fetch an email message
Contacts
- List contacts
- Get a contact
- Create a contact
- Update a contact
- Delete a contact
WhatsApp templates
- Send a WhatsApp template
- Create a WhatsApp template
- List WhatsApp templates
Board cards
- Create a card
- Update a card
- Delete a card
Reports
- Get reporting metrics
- Get agent performance
- Get ticket details report
Events Trengo can send to a Tray.ai webhook trigger
- Inbound message received
- Outbound message sent
- Internal note created
- Ticket created
- Ticket assigned
- Ticket closed
- Ticket reopened
- Ticket label added
- Voice call ended
- Voice call missed
- Contact created
- Contact updated
Checked against Trengo's own documentation on 2026-10-22
How Tray.ai makes this work
Trengo plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 700+ connectors with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Trengo — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Trengo actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →More customer service apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every customer service connector →
Frequently asked questions
What can a Tray.ai workflow do in Trengo?
+
The Trengo API documents 21 actions across 6 resources (Tickets, Messages, Contacts, WhatsApp templates, Board cards, Reports). For example: List tickets; Send a ticket message; List contacts. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Trengo?
+
The Trengo API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which Trengo events can start a Tray.ai workflow?
+
Trengo sends 12 events to a webhook URL, for example: Inbound message received; Outbound message sent; Internal note created; Ticket created; Ticket assigned; Ticket closed; Ticket reopened; Ticket label added. A Tray.ai webhook trigger receives them and starts a workflow.
See Trengo working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.