---
title: "Connect incident.io to Emelia - APIANT.ai"
description: "When \"New Incident\" fires in incident.io, your agent runs \"Add Contact to a Campaign\" in Emelia."
canonical: "https://apiant.ai/connect/incident-io-to-emelia"
---

# Connect incident.io to Emelia

When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add Contact to a Campaign** in [Emelia](https://apiant.ai/connections/emelia). Describe the whole flow and it is built, tested on every scenario and kept running.

incident.io **1** trigger incident.io **10** actions Emelia **16** 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 Emelia 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 can start in Emelia

- When **New Incident** in incident.io then **Add Contact to a Campaign** in Emelia
- When **New Incident** in incident.io then **Add Contact to a List** in Emelia

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 Emelia

## Triggers and actions 1 trigger · 26 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.

- Action

**Add campaign**

Creates a new email campaign in Emelia with the given name and time zone.

- Action

**Add Contact to a Campaign**

Adds a contact to an Emelia campaign.

- Action

**Add Contact to a List**

Adds a single contact to an Emelia list (and to any campaigns using that list), optionally updating it if it already exists.

- Action

**Add Contact to Blacklist**

Adds an email address or an entire domain to your Emelia blacklist so it is never contacted by your campaigns.

- Action

**Add list**

Creates a new, empty contact list in Emelia.

- Action

**Delete contact**

Deletes a contact (and its company data) from an Emelia contact list; the removal also propagates to campaigns using that list.

- Action

**Get campaign**

Returns the full configuration of an Emelia campaign, including the contact lists attached to it and excluded from it.

- Action

**Get campaign statistics**

Returns sending, open, click and reply statistics for an Emelia campaign, overall and per step.

- Action

**Get contact**

Returns a single contact from an Emelia contact list.

- Action

**List Campaign Contacts**

Returns the contacts enrolled in an email campaign, optionally filtered by an engagement event or a search term.

- Action

**List campaigns**

Returns all campaigns in your Emelia account.

- Action

**List contacts**

Returns the contacts in an Emelia contact list, optionally filtered by search text or an exact email or LinkedIn URL.

- Action

**Search Contact**

Searches a contact list for contacts by exact email, LinkedIn URL, or free text, and returns the matches.

- Action

**Set a Custom Field to a Contact**

Sets the value of a custom field on a contact in an Emelia campaign, identified by email or LinkedIn profile URL.

- Action

**Test Webhook**

Sends a test call to an existing Emelia webhook.

- Action

**Update contact**

Updates an Emelia contact's values; fields you don't send stay unchanged, and changes propagate to campaigns using the contact's list.

## 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)
- [ **Emelia** Emelia is an all-in-one cold-emailing tool where you can scale easily your cold email, scrape data, and find...](https://apiant.ai/connections/emelia)

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 Emelia

- [ **Benetics to Emelia** Benetics is a construction efficiency platform built in the cloud.](https://apiant.ai/connect/benetics-to-emelia)
- [ **HubSpot to Emelia** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-emelia)
- [ **Salesforce to Emelia** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-emelia)
- [ **Slack to Emelia** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-emelia)
- [ **Google Sheets to Emelia** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-emelia)
- [ **Gmail to Emelia** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-emelia)

Questions

## incident.io and Emelia, 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 Emelia when something happens in incident.io?

Any of Emelia's 16 actions, including Update contact, Add campaign, Add Contact to a Campaign and Add Contact to a List. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Emelia to incident.io?

Emelia has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Emelia's API documentation and adds it.

###

### Do I have to build a connector for incident.io or Emelia?

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