---
title: "Connect HelpDesk and incident.io - APIANT.ai"
description: "When \"New Message in a Ticket\" fires in HelpDesk, your agent runs \"Find Users On-Call\" in incident.io."
canonical: "https://apiant.ai/connect/helpdesk-to-incident-io"
---

# Connect HelpDesk and incident.io

When **New Message in a Ticket** fires in [HelpDesk](https://apiant.ai/connections/helpdesk), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Add Followers to Ticket** in HelpDesk. Describe the whole flow and it is built, tested on every scenario and kept running.

HelpDesk **2** triggers HelpDesk **20** actions incident.io **1** trigger incident.io **10** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want HelpDesk and incident.io 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 HelpDesk and incident.io can do together

### From HelpDesk to incident.io

- When **New Message in a Ticket** in HelpDesk then **Find Users On-Call** in incident.io
- When **New Ticket** in HelpDesk then **Add follow-up** in incident.io

### From incident.io to HelpDesk

- When **New Incident** in incident.io then **Add Followers to Ticket** in HelpDesk
- When **New Incident** in incident.io then **Add Tags to Ticket** in HelpDesk

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 HelpDesk and incident.io

## Triggers and actions 3 triggers · 30 actions

- Trigger

**New Message in a Ticket**

- Trigger

**New Ticket**

- Action

**Add Canned Response**

Create a new canned response.

- Action

**Add Followers to Ticket**

- Action

**Add Tags to Ticket**

- Action

**Create Ticket**

- Action

**Create Upload Transaction**

- Action

**Delete Canned Response**

Delete a canned response by ID.

- Action

**Delete Ticket**

Delete a ticket by ID.

- Action

**Find Tickets**

- Action

**Get Agent**

Retrieve a single agent by ID.

- Action

**Get Canned Response**

Retrieve a single canned response by ID.

- Action

**Get Team**

Retrieve a single team by ID.

- Action

**Get Ticket**

Retrieve a single ticket by ID.

- Action

**List Agents**

List all agents.

- Action

**List Canned Responses**

List all canned responses.

- Action

**List Teams**

List all teams.

- Action

**Update Agent**

Update an existing agent by ID.

- Action

**Update Canned Response**

Update an existing canned response by ID.

- Action

**Update Team**

Update an existing team by ID.

- Action

**Update Ticket / Send Reply**

- Action

**Upload Attachment During Transaction**

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

## Each app on its own

- [ **HelpDesk** HelpDesk is a ticketing software for effortless customer support](https://apiant.ai/connections/helpdesk)
- [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io)

Reviews

## What our customers say

## More from HelpDesk

- [ **HelpDesk to Geocode.xyz** Geocode.xyz is a worldwide geocoding service.](https://apiant.ai/connect/helpdesk-to-geocode-xyz)
- [ **HelpDesk to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/helpdesk-to-linkedin)
- [ **HelpDesk to Facebook** Facebook is a social media and advertising platform used by individuals and businesses to connect, share...](https://apiant.ai/connect/helpdesk-to-facebook)
- [ **HelpDesk to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/helpdesk-to-anthropic)
- [ **HelpDesk to Supabase** Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...](https://apiant.ai/connect/helpdesk-to-supabase)
- [ **HelpDesk to ElevenLabs** ElevenLabs is an AI audio research and deployment company.](https://apiant.ai/connect/helpdesk-to-elevenlabs)

## More into incident.io

- [ **HubSpot to incident.io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-incident-io)
- [ **Google Sheets to incident.io** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-incident-io)
- [ **Gmail to incident.io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-incident-io)
- [ **Google Calendar to incident.io** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-incident-io)
- [ **Google Drive to incident.io** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-incident-io)
- [ **ActiveCampaign to incident.io** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-incident-io)

Questions

## HelpDesk and incident.io, answered

###

### What can start an automation from HelpDesk?

Any of HelpDesk's 2 triggers in the catalog, including New Message in a Ticket and New Ticket. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in incident.io when something happens in HelpDesk?

Any of incident.io's 10 actions, including Create Incident, Add follow-up, Add incident update and Find Users On-Call. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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 HelpDesk and incident.io 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.
