---
title: "Connect Fellow and incident.io - APIANT.ai"
description: "When \"New recording\" fires in Fellow, your agent runs \"Find Users On-Call\" in incident.io."
canonical: "https://apiant.ai/connect/fellow-to-incident-io"
---

# Connect Fellow and incident.io

When **New recording** fires in [Fellow](https://apiant.ai/connections/fellow), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Complete Action Item** in Fellow. Describe the whole flow and it is built, tested on every scenario and kept running.

Fellow **1** trigger Fellow **11** 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 Fellow 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 Fellow and incident.io can do together

### From Fellow to incident.io

- When **New recording** in Fellow then **Find Users On-Call** in incident.io
- When **New recording** in Fellow then **Add follow-up** in incident.io

### From incident.io to Fellow

- When **New Incident** in incident.io then **Complete Action Item** in Fellow
- When **New Incident** in incident.io then **Get action item** in Fellow

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

## Triggers and actions 2 triggers · 21 actions

- Trigger

**New recording**

Triggers when a new meeting recording is created in Fellow.

- Action

**Add Talking Point**

Adds a talking point to the end of a Fellow meeting note's agenda, leaving the existing agenda content in place.

- Action

**Archive action item**

Archives a Fellow action item by marking it as won't do, and returns the updated action item.

- Action

**Complete Action Item**

Marks a Fellow action item as complete, or reopens it as incomplete, and returns the updated action item.

- Action

**Delete note**

Permanently deletes a Fellow meeting note. Requires an API key with super admin (privileged) access.

- Action

**Delete recording**

Deletes a Fellow meeting recording by its ID. Requires an API key with super admin privileges.

- Action

**Get action item**

Returns a single Fellow action item by its ID, including its text, status, due date, assignees and the note it belongs to.

- Action

**Get AI Note**

Returns a Fellow meeting note by its ID, including its title, meeting details, attendees, linked recordings and the note content as markdown.

- Action

**Get recording**

Returns a Fellow meeting recording, including its transcript, AI notes and the note it belongs to.

- Action

**List action items**

Returns the Fellow action items you have access to, optionally narrowed by who they are assigned to, completion, archive status, AI detection, and created or updated dates.

- Action

**List notes**

Returns the meeting notes you can access in Fellow, optionally filtered by meeting, channel, title, attendees, or created/updated dates, with optional note content.

- Action

**List recordings**

Returns the meeting recordings in your Fellow workspace, optionally filtered by calendar event, channel, title or created/updated dates, with transcripts and AI notes on request.

- 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

- [ **Fellow** Fellow is a privacy-focused AI meeting assistant that records and summarizes meetings with enterprise-grade...](https://apiant.ai/connections/fellow)
- [ **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 Fellow

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

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

## Fellow and incident.io, answered

###

### What can start an automation from Fellow?

Any of Fellow's 1 trigger in the catalog, including New recording. 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 Fellow?

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 Fellow?

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

###

### Do I have to build a connector for Fellow 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 Fellow 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.
