# Trengo integrations: tickets and messages

> Create a ticket, send a ticket message and create a contact in Trengo, and start a workflow when Trengo sends “Inbound message received”.

**Canonical page:** https://tray.ai/connectors/trengo-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

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.

## Use cases

### Tickets

Read, create, and update tickets in Trengo from any Tray.ai workflow. The Trengo API covers calls such as list tickets and create a ticket.

- List tickets
- Create a ticket
- Assign a ticket

### Messages

Read and create messages in Trengo from any Tray.ai workflow. The Trengo API covers calls such as send a ticket message and list ticket messages.

- Send a ticket message
- List ticket messages
- Fetch an email message

### Contacts

Read, create, update, and delete contacts in Trengo from any Tray.ai workflow. The Trengo API covers calls such as list contacts and get a contact.

- List contacts
- Get a contact
- Create a contact

### WhatsApp templates

Read and create whatsapp templates in Trengo from any Tray.ai workflow. The Trengo API covers calls such as send a WhatsApp template and create a WhatsApp template.

- Send a WhatsApp template
- Create a WhatsApp template
- List WhatsApp templates

### Board cards

Create, update, and delete board cards in Trengo from any Tray.ai workflow. The Trengo API covers calls such as create a card and update a card.

- Create a card
- Update a card
- Delete a card

### Reports

Read reports in Trengo from any Tray.ai workflow. The Trengo API covers calls such as get reporting metrics and get agent performance.

- Get reporting metrics
- Get agent performance
- Get ticket details report

## Challenges Tray.ai solves

### Keeping Trengo credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Trengo credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Trengo API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Trengo API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Trengo?

Yes. Tray.ai connects to Trengo through the HTTP Connector, which calls the Trengo API directly. Any call the Trengo API documents can run as a step in a Tray.ai workflow.

### 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.

### Can I get a dedicated Trengo connector?

Trengo runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Trengo connector from the Trengo API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/