Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

Trengo

Manage omnichannel inbox tickets, contacts, and messages in Trengo.

Base URL: https://app.trengo.com/api/v2
Auth: Authorization: Bearer <apiKey>
Docs: https://developers.trengo.com/

Operations

Operation	Description	Key Inputs
`list_tickets`	List tickets with optional filters	`status`, `contactId`, `page`
`create_ticket`	Open a new ticket on a channel	`channelId` (required), `contactId` (required), `subject`
`close_ticket`	Close an existing ticket	`ticketId` (required)
`send_message`	Send a message or internal note to a ticket	`ticketId` (required), `message` (required), `internalNote`, `subject`
`list_contacts`	List or search contacts	`searchTerm`, `page`
`assign_ticket`	Assign a ticket to a user or team	`ticketId` (required), `assignType` (`user`/`team`), `userId` or `teamId`

API Key Setup

In Trengo, go to Settings > Apps & Integrations > API.
Under Personal Access Tokens, click Create token.
Copy the token — it is shown only once.
Paste it in the apiKey field of this tool.

Examples

List open tickets

{
  "apiKey": "YOUR_TOKEN",
  "operation": "list_tickets",
  "status": "OPEN"
}

Create a ticket

{
  "apiKey": "YOUR_TOKEN",
  "operation": "create_ticket",
  "channelId": "736",
  "contactId": "1",
  "subject": "Support question"
}

Send a message

{
  "apiKey": "YOUR_TOKEN",
  "operation": "send_message",
  "ticketId": "2501567",
  "message": "Thank you for reaching out! We will get back to you shortly."
}

Send an internal note

{
  "apiKey": "YOUR_TOKEN",
  "operation": "send_message",
  "ticketId": "2501567",
  "message": "Escalating to tier 2 — customer is premium.",
  "internalNote": "true"
}

Close a ticket

{
  "apiKey": "YOUR_TOKEN",
  "operation": "close_ticket",
  "ticketId": "2501567"
}

Assign ticket to a user

{
  "apiKey": "YOUR_TOKEN",
  "operation": "assign_ticket",
  "ticketId": "2501567",
  "assignType": "user",
  "userId": "42"
}

Search contacts

{
  "apiKey": "YOUR_TOKEN",
  "operation": "list_contacts",
  "searchTerm": "[email protected]"
}

Published Outputs

Field	Description
`result`	JSON string of the Trengo API response body
`status`	`success` or `error_<httpCode>`

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
httpStatus
result
status
validOperations

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	Bearer token from Trengo Settings > API > Personal Access Tokens.
`operation`	string	yes	—	One of: list_tickets, create_ticket, close_ticket, send_message, list_contacts, assign_ticket
`ticketId`	string	no	—	Ticket ID (required for close_ticket, send_message, assign_ticket).
`status`	string	no	—	Filter tickets by status: OPEN, ASSIGNED, CLOSED, INVALID (for list_tickets).
`contactId`	string	no	—	Contact ID (for create_ticket or filter list_tickets).
`channelId`	string	no	—	Channel ID (required for create_ticket).
`subject`	string	no	—	Ticket subject (optional for create_ticket; email subject for send_message).
`message`	string	no	—	Message body (required for send_message).
`internalNote`	string	no	—	Set to 'true' to send message as an internal note (for send_message).
`assignType`	string	no	—	Assignment type: 'user' or 'team' (required for assign_ticket).
`userId`	string	no	—	User ID (for assign_ticket when assignType is 'user').
`teamId`	string	no	—	Team ID (for assign_ticket when assignType is 'team').
`searchTerm`	string	no	—	Search term to filter contacts by name, email, or phone (for list_contacts).
`page`	string	no	—	Pagination page number (default 1).