--- title: "Connect Heartbeat and Trengo - APIANT.ai" description: "When \"Course Completed\" fires in Heartbeat, your agent runs \"Add internal note to ticket\" in Trengo." canonical: "https://apiant.ai/connect/heartbeat-to-trengo" --- # Connect Heartbeat and Trengo When **Course Completed** fires in [Heartbeat](https://apiant.ai/connections/heartbeat), your agent runs **Add internal note to ticket** in [Trengo](https://apiant.ai/connections/trengo), or **New Internal Note** in Trengo to **Create Event** in Heartbeat. Describe the whole flow and it is built, tested on every scenario and kept running. Heartbeat **4** triggers Heartbeat **6** actions Trengo **3** triggers Trengo **15** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Heartbeat and Trengo 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 Heartbeat and Trengo can do together ### From Heartbeat to Trengo - When **Course Completed** in Heartbeat then **Add internal note to ticket** in Trengo - When **New Event** in Heartbeat then **Add ticket** in Trengo ### From Trengo to Heartbeat - When **New Internal Note** in Trengo then **Create Event** in Heartbeat - When **New Outbound Message** in Trengo then **Deactivate User** in Heartbeat 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 Heartbeat and Trengo ## Triggers and actions 7 triggers ยท 21 actions - Trigger **Abandoned Invitation Link** Triggers when someone enters their information in an invitation link, but does not make a purchase or create their account. This will trigger after 4 hours, if the user still has not made a purchase or created their account. - Trigger **Course Completed** Triggers when a user completes a course. - Trigger **New Event** Triggers when a new event is created. - Trigger **New Event RSVP** Triggers when someone RSVPs to an event. - Action **Create Event** Creates an event in a Heartbeat community and optionally invites people or groups. - Action **Create Group** Creates a group in a Heartbeat community, optionally nested under another group and seeded with members. - Action **Create Thread** Posts a new thread in a Heartbeat channel. - Action **Deactivate User** Removes a person's access to a Heartbeat community by email. Their threads, comments and messages stay in place. - Action **List Channels** Returns all channels in the Heartbeat community, with each channel's name, emoji and type. - Action **List Threads** Returns all threads posted in a Heartbeat channel, with each thread's body, author, link and creation time. - 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. ## Each app on its own - [ **Heartbeat** Heartbeat is a platform for online communities, where members can talk with each other, read content, and...](https://apiant.ai/connections/heartbeat) - [ **Trengo** Trengo is a team collaboration tool to manage conversations from channels such as web chat, email and...](https://apiant.ai/connections/trengo) Reviews ## What our customers say ## More from Heartbeat - [ **Heartbeat to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/heartbeat-to-hubspot) - [ **Heartbeat to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/heartbeat-to-salesforce) - [ **Heartbeat to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/heartbeat-to-slack) - [ **Heartbeat to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/heartbeat-to-mailchimp) - [ **Heartbeat to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/heartbeat-to-stripe) - [ **Heartbeat to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/heartbeat-to-shopify) ## More into Trengo - [ **OpenAI to Trengo** OpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...](https://apiant.ai/connect/openai-to-trengo) - [ **CloudConvert to Trengo** CloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...](https://apiant.ai/connect/cloudconvert-to-trengo) - [ **elmah.io to Trengo** Cloud logging for.NET web applications using ELMAH.](https://apiant.ai/connect/elmah-io-to-trengo) - [ **Postman to Trengo** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-trengo) - [ **HubSpot to Trengo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-trengo) - [ **Salesforce to Trengo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-trengo) Questions ## Heartbeat and Trengo, answered ### ### What can start an automation from Heartbeat? Any of Heartbeat's 4 triggers in the catalog, including Course Completed, New Event, New Event RSVP and Abandoned Invitation Link. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Trengo when something happens in Heartbeat? Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Trengo to Heartbeat? Yes. When something happens in Trengo, your agent can act in Heartbeat too. This page covers both directions: Trengo's triggers and Heartbeat's actions are listed here as well. ### ### Do I have to build a connector for Heartbeat or Trengo? 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 Heartbeat and Trengo 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.