---
title: "Connect ilert and Trengo - APIANT.ai"
description: "When \"New or Updated Incident\" fires in ilert, your agent runs \"Add internal note to ticket\" in Trengo."
canonical: "https://apiant.ai/connect/ilert-to-trengo"
---

# Connect ilert and Trengo

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

ilert **1** trigger ilert **12** 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 ilert 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 ilert and Trengo can do together

### From ilert to Trengo

- When **New or Updated Incident** in ilert then **Add internal note to ticket** in Trengo
- When **New or Updated Incident** in ilert then **Add ticket** in Trengo

### From Trengo to ilert

- When **New Internal Note** in Trengo then **Find User on Call** in ilert
- When **New Outbound Message** in Trengo then **Add Alert** in ilert

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 ilert and Trengo

## Triggers and actions 4 triggers · 27 actions

- Trigger

**New or Updated Incident**

Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.

- Action

**Accept Incident**

Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

- Action

**Add Alert**

Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).

- Action

**Add maintenance window**

Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

- Action

**Create Incident**

Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.

- Action

**Find User on Call**

Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.

- Action

**Get alert**

Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

- Action

**Get incident**

Returns a single ilert incident by its id, including its status, severity, affected services and responders.

- Action

**Get maintenance window**

Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

- Action

**List Alert Sources**

Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

- Action

**List incidents**

Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

- Action

**List users**

Returns the users in your ilert account, with their name, email, role and contact settings.

- Action

**Resolve Incident**

Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

- 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

- [ **ilert** ilert is a platform for alerting, on-call management, and status pages.](https://apiant.ai/connections/ilert)
- [ **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 ilert

- [ **ilert to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/ilert-to-salesforce)
- [ **ilert to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/ilert-to-slack)
- [ **ilert to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/ilert-to-mailchimp)
- [ **ilert to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/ilert-to-stripe)
- [ **ilert to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/ilert-to-shopify)
- [ **ilert to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/ilert-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

## ilert and Trengo, answered

###

### What can start an automation from ilert?

Any of ilert's 1 trigger in the catalog, including New or Updated 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 ilert?

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 ilert?

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

###

### Do I have to build a connector for ilert 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 ilert 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.
