---
title: "Connect Trengo and Ventrata - APIANT.ai"
description: "When \"New Internal Note\" fires in Trengo, your agent runs \"Add booking\" in Ventrata."
canonical: "https://apiant.ai/connect/trengo-to-ventrata"
---

# Connect Trengo and Ventrata

When **New Internal Note** fires in [Trengo](https://apiant.ai/connections/trengo), your agent runs **Add booking** in [Ventrata](https://apiant.ai/connections/ventrata), or **Updated Booking** in Ventrata to **Add internal note to ticket** in Trengo. Describe the whole flow and it is built, tested on every scenario and kept running.

Trengo **3** triggers Trengo **15** actions Ventrata **1** trigger Ventrata **11** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Trengo and Ventrata to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Trengo and Ventrata can do together

### From Trengo to Ventrata

- When **New Internal Note** in Trengo then **Add booking** in Ventrata
- When **New Outbound Message** in Trengo then **Update booking** in Ventrata

### From Ventrata to Trengo

- When **Updated Booking** in Ventrata then **Add internal note to ticket** in Trengo
- When **Updated Booking** in Ventrata then **Add ticket** in Trengo

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Trengo and Ventrata

## Triggers and actions 4 triggers · 26 actions

- Trigger

**New Internal Note**

Fires when an internal note is added to a Trengo ticket.

- Trigger

**New Outbound Message**

Triggers when an outbound message is created.

- Trigger

**Ticket Label Added**

Triggers when a label is added to a conversation.

- Action

**Add internal note to ticket**

Adds an internal note (visible only to agents) to a Trengo ticket.

- Action

**Add ticket**

Create a new support ticket.

- Action

**Add ticket label**

Attaches an existing label to a Trengo ticket.

- Action

**Create a Contact**

Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.

- Action

**Create webhook**

Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.

- Action

**Delete contact**

Delete a contact by id.

- Action

**Delete ticket**

Delete a ticket by id.

- Action

**Find a Contact**

Returns the Trengo contacts that match the search term.

- Action

**Get contact**

Retrieve a single Trengo contact by its id.

- Action

**Get webhook**

Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.

- Action

**List contacts**

List all contacts.

- Action

**List labels**

Lists the ticket labels defined in the Trengo account (first page).

- Action

**List tickets**

Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.

- Action

**Send a Message**

Sends a reply message on an existing Trengo ticket, over the ticket's own channel.

- Action

**Update contact**

Update an existing contact by id.

- Trigger

**Updated Booking**

Triggers when any booking is created, updated, cancelled, or redeemed, including changes to customer details, products, options, quantities, or status.

- Action

**Add booking**

Reserves availability by creating an ON_HOLD booking. Confirm it afterwards with Confirm booking.

- Action

**Confirm booking**

/bookings/{uuid}/confirm - confirm an on-hold booking with contact details (OCTO Core).

- Action

**Delete booking**

/bookings/{uuid} - cancel a booking with optional reason (OCTO Core).

- Action

**Find availability**

/availability - search availability for a product/option over a date range or specific dates (OCTO Core).

- Action

**Find availability calendar**

/availability/calendar - daily availability summary for a product/option over a date range (OCTO Core).

- Action

**Find Booking**

Find bookings by reference, date, contact details or other filters. At least one primary filter is required.

- Action

**Get booking**

/bookings/{uuid} - retrieve a booking by UUID (OCTO Core).

- Action

**Get product**

/products/{id} - retrieve one product with its options and units (OCTO Core).

- Action

**Get supplier**

Returns the supplier the connected API key belongs to (name, reference, website, contact details).

- Action

**List products**

/products - list all bookable products for the supplier (OCTO Core).

- Action

**Update booking**

/bookings/{uuid} - amend an existing booking (date/time, units, contact) (OCTO Core).

## Each app on its own

- [ **Trengo** Trengo is a team collaboration tool to manage conversations from channels such as web chat, email and...](https://apiant.ai/connections/trengo)
- [ **Ventrata** Ventrata is a ticketing platform for high-volume attractions, tours, and activities that manages ticket...](https://apiant.ai/connections/ventrata)

Reviews

## What our customers say

## More from Trengo

- [ **Trengo to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/trengo-to-zoom)
- [ **Trengo to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/trengo-to-twilio)
- [ **Trengo to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/trengo-to-typeform)
- [ **Trengo to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/trengo-to-webflow)
- [ **Trengo to Wix** The Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...](https://apiant.ai/connect/trengo-to-wix)
- [ **Trengo to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/trengo-to-linkedin)

## More into Ventrata

- [ **HubSpot to Ventrata** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ventrata)
- [ **Salesforce to Ventrata** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-ventrata)
- [ **Slack to Ventrata** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-ventrata)
- [ **Google Sheets to Ventrata** Google Sheets](https://apiant.ai/connect/google-sheets-to-ventrata)
- [ **Gmail to Ventrata** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ventrata)
- [ **Google Calendar to Ventrata** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ventrata)

Questions

## Trengo and Ventrata, answered

###

### What can start an automation from Trengo?

Any of Trengo's 3 triggers in the catalog, including New Internal Note, New Outbound Message and Ticket Label Added. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Ventrata when something happens in Trengo?

Any of Ventrata's 11 actions, including Update booking, Add booking, Confirm booking and Find availability. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Ventrata to Trengo?

Yes. When something happens in Ventrata, your agent can act in Trengo too. This page covers both directions: Ventrata's triggers and Trengo's actions are listed here as well.

###

### Do I have to build a connector for Trengo or Ventrata?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Trengo and Ventrata without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
