--- title: "Connect incident.io and Zendesk - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add Comment to Ticket\" in Zendesk." canonical: "https://apiant.ai/connect/incident-io-to-zendesk" --- # Connect incident.io and Zendesk When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add Comment to Ticket** in [Zendesk](https://apiant.ai/connections/zendesk), or **New Messaging Conversation** in Zendesk 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 **11** actions Zendesk **3** triggers Zendesk **18** 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 Zendesk 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 Zendesk can do together ### From incident.io to Zendesk - When **New Incident** in incident.io then **Add Comment to Ticket** in Zendesk - When **New Incident** in incident.io then **Create Ticket** in Zendesk ### From Zendesk to incident.io - When **New Messaging Conversation** in Zendesk then **Find Users On-Call** in incident.io - When **New Ticket** in Zendesk 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 Zendesk ## Triggers and actions 4 triggers · 29 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 **Update incident** Edits an existing incident's name, summary, severity, status, call link, Slack channel name, custom fields, role assignments or timestamps. Only the values you provide are changed. - Trigger **New Messaging Conversation** Triggers when a customer starts a new conversation through Zendesk messaging (the web widget, mobile SDK or a social messaging channel). Each conversation arrives as its Zendesk ticket. - Trigger **New Ticket** Polling trigger that fires when a new ticket is created. - Trigger **New User** Polling trigger that fires when a new user is created. - Action **Add Comment to Ticket** Adds a public or private comment to an existing ticket. - Action **Create Organization** Creates a new organization. - Action **Create Ticket** Creates a new ticket in Zendesk. - Action **Create User** Creates a new user (end-user or agent). - Action **Delete Ticket** Deletes a ticket by ID. - Action **Delete User** Soft-deletes a user by ID. - Action **Get Messaging User ID** Returns the Zendesk messaging ID for a user, so their messaging conversation can be looked up in Zendesk Messaging. - Action **Get Organization** Retrieves a single organization by ID. - Action **Get Ticket** Retrieves a single ticket by ID. - Action **Get User** Retrieves a single user by ID. - Action **List Organizations** Lists organizations in the account. - Action **List Ticket Comments** Lists all comments on a ticket. - Action **List Tickets** Lists tickets in the account. - Action **Search** Runs a Zendesk search query across tickets, users, and organizations. - Action **Search Users** Searches users by query (name, email, etc.). - Action **Update Organization** Updates an existing organization by ID. - Action **Update Ticket** Updates an existing ticket by ID. - Action **Update User** Updates an existing user 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) - [ **Zendesk** Zendesk is a web-based help desk and customer support platform for managing tickets, users, and organizations.](https://apiant.ai/connections/zendesk) 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 Zendesk - [ **HubSpot to Zendesk** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-zendesk) - [ **Salesforce to Zendesk** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-zendesk) - [ **Slack to Zendesk** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-zendesk) - [ **Google Sheets to Zendesk** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-zendesk) - [ **Gmail to Zendesk** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-zendesk) - [ **Google Calendar to Zendesk** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-zendesk) Questions ## incident.io and Zendesk, 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 Zendesk when something happens in incident.io? Any of Zendesk's 18 actions, including Create Organization, Create Ticket, Create User and Update Organization. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Zendesk to incident.io? Yes. When something happens in Zendesk, your agent can act in incident.io too. This page covers both directions: Zendesk's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Zendesk? 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 Zendesk 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.