Integration

Trengo integration

Trengo API v2, the shared inbox that merges email, WhatsApp, SMS, voice and social channels into one ticket stream. List and filter tickets by status, channel, label and agent, open one, read its messages and post a reply or an internal note, assign a ticket to a user or a team and close it with a result, manage the contact database, start a WhatsApp conversation from an approved template, and read the voice channels of the account.

Connect Trengo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Trengo.Built from the 13 Trengo tools below, on the connection you add once.

Common Trengo use cases

honouring a data erasure request
routing a billing question to the finance team
moving a contact into a VIP group after an upgrade
reading a customer's stored details before answering
triaging the unassigned queue at the start of a shift
summarising a ticket before handing it to another agent
sending the drafted answer on the channel the customer used
creating the contact record before opening an outbound ticket
closing a ticket once the customer confirms the issue is solved
resolving an email address to a contact before opening a ticket

What you can do with Trengo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 5 operations

create_contactCreate contactPOSTCreates a contact on a channel.
delete_contactDelete contactDELETEPermanently deletes a contact.
get_contactGet contactGETReturns a single contact with its custom field values.
list_contactsList contactsGETLists contacts and searches them by name, email or phone number.
update_contactUpdate contactPUTRenames a contact or changes the contact groups it belongs to.

Ticket, 4 operations

assign_ticketAssign ticketPOSTAssigns a ticket to an agent or routes it to a team.
close_ticketClose ticketPOSTCloses a ticket and can tag it with a ticket result.
create_ticketCreate ticketPOSTOpens a ticket for an existing contact on a given channel.
list_ticketsList ticketsGETLists tickets filtered by status, channel, label, agent or contact.

Message, 3 operations

list_ticket_messagesList ticket messagesGETReads the message history of a ticket, page by page.
send_ticket_messageSend ticket messagePOSTReplies to a ticket on its own channel, or leaves an internal note.
send_whatsapp_templateSend whatsapp templatePOSTSends an approved WhatsApp template to open or reopen a conversation.

Channel, 1 operation

list_voice_channelsList voice channelsGETLists the voice channels with their phone numbers.

Use Trengo from Claude Code, Cursor or Codex

Connect Trengo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Trengo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Trengo

Create your workspace
Sign up free. Nothing to install.
Connect Trengo once
Add your Trengo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Trengo integration FAQ

What can you do with the Trengo integration?

LiveContext exposes 13 operations on Trengo, covering contact, ticket, message and channel. Common uses include honouring a data erasure request, routing a billing question to the finance team and moving a contact into a VIP group after an upgrade.