--- title: "Connect incident.io and Intercom - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add note to contact\" in Intercom." canonical: "https://apiant.ai/connect/incident-io-to-intercom" --- # Connect incident.io and Intercom When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add note to contact** in [Intercom](https://apiant.ai/connections/intercom), or **New company** in Intercom 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 Intercom **4** triggers Intercom **24** 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 Intercom 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 Intercom can do together ### From incident.io to Intercom - When **New Incident** in incident.io then **Add note to contact** in Intercom - When **New Incident** in incident.io then **Add tag to contact** in Intercom ### From Intercom to incident.io - When **New company** in Intercom then **Find Users On-Call** in incident.io - When **New conversation** in Intercom 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 Intercom ## Triggers and actions 5 triggers · 34 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 company** Fires when a new company is created. - Trigger **New conversation** Polls for conversations, most recently updated first. Fires for each new conversation. - Trigger **New or updated contact** Polls for contacts, most recently updated first. Fires for each new or updated contact. - Trigger **New ticket** Fires when a new ticket is created. - Action **Add note to contact** Adds a note to the specified contact as the specified admin. - Action **Add note to conversation** Adds an internal note to the specified conversation as an admin. - Action **Add tag to contact** Attaches a tag to the specified contact. - Action **Assign conversation** Assigns the conversation to an admin or team. - Action **Close conversation** Closes the specified conversation. - Action **Create message** Creates an admin-initiated email or in-app message to a contact. - Action **Delete company** Delete a company by ID. - Action **Delete contact** Deletes a contact by ID. - Action **Find admin by email** Fetches an admin's details. Lists all admins; match by email. - Action **Find contact by email** Searches contacts by email and returns matches. - Action **Find tickets** Search tickets by criteria. - Action **Get company** Retrieve a company by ID. - Action **Get contact** Fetches a contact's details by ID. - Action **Get conversation** Fetches a conversation's details by ID. - Action **Get ticket** Retrieve a ticket by ID. - Action **List companies** List all companies. - Action **List segments** List all segments. - Action **List tags** Lists all tags for the workspace. - Action **Open conversation** Opens (marks open) the specified conversation. - Action **Remove tag from contact** Detaches a tag from the specified contact. - Action **Send conversation reply** Sends a reply to the specified conversation as an admin. - Action **Snooze conversation** Snoozes the specified conversation until the given unix timestamp. - Action **Start conversation** Starts a new conversation with the specified contact. - Action **Track event** Submit a data event for a contact. ## 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) - [ **Intercom** Intercom is a customer communications platform for support, engagement, and marketing.](https://apiant.ai/connections/intercom) 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 Intercom - [ **Google Sheets to Intercom** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-intercom) - [ **Google Calendar to Intercom** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-intercom) - [ **Mailchimp to Intercom** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-intercom) - [ **Typeform to Intercom** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/typeform-to-intercom) - [ **Freshworks CRM to Intercom** Freshworks CRM (Freshsales Suite) — manage contacts, sales accounts, deals, notes, tasks, and appointments.](https://apiant.ai/connect/freshworks-crm-to-intercom) - [ **Capsule CRM to Intercom** Capsule is an online hosted CRM system for individuals, small businesses and sales teams wanting a simple...](https://apiant.ai/connect/capsule-crm-to-intercom) Questions ## incident.io and Intercom, 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 Intercom when something happens in incident.io? Any of Intercom's 24 actions, including Create message, Send conversation reply, Add note to contact and Add note to conversation. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Intercom to incident.io? Yes. When something happens in Intercom, your agent can act in incident.io too. This page covers both directions: Intercom's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Intercom? 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 Intercom 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.