---
title: "Connect incident.io and Sender - APIANT.ai"
description: "When \"New Incident\" fires in incident.io, your agent runs \"Unsubscribe Email\" in Sender, or \"New Group\" in Sender to \"Find Users On-Call\" in incident.io."
canonical: "https://apiant.ai/connect/incident-io-to-sender"
---

# Connect incident.io and Sender

When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Unsubscribe Email** in [Sender](https://apiant.ai/connections/sender), or **New Group** in Sender 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 Sender **4** triggers Sender **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 incident.io and Sender 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 Sender can do together

### From incident.io to Sender

- When **New Incident** in incident.io then **Unsubscribe Email** in Sender
- When **New Incident** in incident.io then **Add group** in Sender

### From Sender to incident.io

- When **New Group** in Sender then **Find Users On-Call** in incident.io
- When **New Subscriber** in Sender 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 Sender

## Triggers and actions 5 triggers · 20 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 Group**

Triggers when a new group is created.

- Trigger

**New Subscriber**

Triggers when a new subscriber is added.

- Trigger

**New Unsubscriber From Group**

Triggers when a subscriber is removed from a group.

- Trigger

**Updated Subscriber**

Triggers when a subscriber is updated.

- Action

**Add group**

Create a new subscriber group.

- Action

**Add Subscriber to Group**

Adds a subscriber to a group.

- Action

**Add / Update Subscriber**

Adds a new subscriber. If subscriber with the same email exists, updates the subscriber's data.

- Action

**Create Campaign**

Creates a draft campaign

- Action

**Get campaign**

Retrieve details of a single campaign by campaign id.

- Action

**Get subscriber**

Retrieve a single subscriber's data by email or subscriber id.

- Action

**List groups**

List all subscriber groups on the account.

- Action

**List subscribers**

List all subscribers on the account, paginated.

- Action

**Remove Subscriber From Group**

Removes a subscriber from a group.

- Action

**Unsubscribe Email**

Unsubscribes an email address.

## 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)
- [ **Sender** Capture leads and turn them into loyal customers through Sender, the easy and affordable email & SMS platform.](https://apiant.ai/connections/sender)

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 Sender

- [ **SureCart to Sender** The new way to sell on WordPress. A simple yet powerful e-commerce platform designed to grow your business...](https://apiant.ai/connect/surecart-to-sender)
- [ **HubSpot to Sender** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sender)
- [ **Salesforce to Sender** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sender)
- [ **Gmail to Sender** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sender)
- [ **Google Calendar to Sender** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sender)
- [ **Google Drive to Sender** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-sender)

Questions

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

Any of Sender's 10 actions, including Create Campaign, Add group, Add Subscriber to Group and Add / Update Subscriber. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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