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

# Connect incident.io to EveryAction

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

incident.io **1** trigger incident.io **10** actions EveryAction **14** 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 EveryAction 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 EveryAction

- When **New Incident** in incident.io then **Add Contact History** in EveryAction
- When **New Incident** in incident.io then **Add Note to Contact** in EveryAction

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 EveryAction

## Triggers and actions 1 trigger · 24 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 a Contribution**

Creates a contribution (donation) for a contact in EveryAction, credited to a designation.

- Action

**Add Activist Codes**

Applies or removes an activist code on a person in EveryAction.

- Action

**Add Canvass Responses**

Records a canvass interaction with a person: either a result code (e.g. not home) or a set of activist code, survey and volunteer activity responses.

- Action

**Add Contact History**

Records a contact attempt (contact history with a result code, such as Not Home or Wrong Number) on a person in EveryAction.

- Action

**Add event**

Creates a new event in EveryAction with its date range, event type, and optional locations, shifts, roles and notes.

- Action

**Add Note to Contact**

Adds a free-form note to a contact (person) in EveryAction, optionally with a category and a contact history record.

- Action

**Add Survey Responses**

Records a contact's answer to a survey question in EveryAction.

- Action

**Create Financial Batch**

Creates a financial batch for grouping contributions under a designation.

- Action

**Create or Update Contact**

Finds a contact matching the details given and updates it, or creates a new contact when no match exists. Returns the contact's VAN ID.

- Action

**Find Contact**

Finds contacts matching the name, address, phone, or email criteria you provide. Matches are case-insensitive and match any value starting with what you enter.

- Action

**Find Financial Batch**

Finds financial batches whose names contain the given text, optionally including unassigned, auto-generated and closed batches.

- Action

**Get activist code**

Returns one activist code by its id, including its name, type, description, script question and status.

- Action

**Subscribe Email**

Finds or creates a contact by email and marks that email address as subscribed.

- Action

**Tag a Contact**

Applies a tag (or source code) to an existing contact in EveryAction.

## 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)
- [ **EveryAction** EveryAction provides nonprofits with customer relationship management, donor management, and fundraising...](https://apiant.ai/connections/everyaction)

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 EveryAction

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

Questions

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

Any of EveryAction's 14 actions, including Create Financial Batch, Create or Update Contact, Add a Contribution and Add Activist Codes. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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