--- title: "Connect incident.io and Trengo - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add internal note to ticket\" in Trengo." canonical: "https://apiant.ai/connect/incident-io-to-trengo" --- # Connect incident.io and Trengo When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add internal note to ticket** in [Trengo](https://apiant.ai/connections/trengo), or **New Internal Note** in Trengo to **Find Users On-Call** in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** 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 incident.io 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 incident.io and Trengo can do together ### From incident.io to Trengo - When **New Incident** in incident.io then **Add internal note to ticket** in Trengo - When **New Incident** in incident.io then **Add ticket** in Trengo ### From Trengo to incident.io - When **New Internal Note** in Trengo then **Find Users On-Call** in incident.io - When **New Outbound Message** in Trengo then **Add follow-up** in incident.io 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 incident.io and Trengo ## Triggers and actions 4 triggers · 25 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - 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 - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **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 incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## 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 ## incident.io and Trengo, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Trengo when something happens in incident.io? 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 incident.io? Yes. When something happens in Trengo, your agent can act in incident.io too. This page covers both directions: Trengo's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io 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 incident.io 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.