---
title: "Connect Fabric and incident.io - APIANT.ai"
description: "When \"New Item\" fires in Fabric, your agent runs \"Find Users On-Call\" in incident.io, or \"New Incident\" in incident.io to \"Add task\" in Fabric."
canonical: "https://apiant.ai/connect/fabric-to-incident-io"
---

# Connect Fabric and incident.io

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

Fabric **1** trigger Fabric **6** actions incident.io **1** trigger incident.io **11** actions

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

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

### From Fabric to incident.io

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

### From incident.io to Fabric

- When **New Incident** in incident.io then **Add task** in Fabric
- When **New Incident** in incident.io then **Create Note** in Fabric

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

## Triggers and actions 2 triggers · 17 actions

- Trigger

**New Item**

Triggers when a new item (note, file, bookmark, folder and more) is added to your Fabric workspace.

- Action

**Add folder**

Creates a new folder in Fabric, optionally inside a parent folder.

- Action

**Add tag**

Creates a new tag in Fabric, optionally attaching it to an item.

- Action

**Add task**

Creates a new task in Fabric with a title and optional description, due date, priority and visibility flags.

- Action

**Create Bookmark**

Creates a bookmark in Fabric from a web URL, saved into the folder or space you choose (or your Inbox).

- Action

**Create Note**

Creates a new note (notepad) in Fabric with the text you provide, in your Inbox or a folder you choose.

- Action

**Find resources**

Searches your Fabric resources by text (keywords or natural language), similar resource, or image, with optional filters by kind, folder, tag, creator and date.

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

## Each app on its own

- [ **Fabric** Fabric is your second brain and self-organizing personal cloud. Remember everything.](https://apiant.ai/connections/fabric)
- [ **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 Fabric

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

## Fabric and incident.io, answered

###

### What can start an automation from Fabric?

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

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

###

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

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

###

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