---
title: "Connect incident.io to F1 API - APIANT.ai"
description: "When \"New Incident\" fires in incident.io, your agent runs \"Find drivers by name\" in F1 API."
canonical: "https://apiant.ai/connect/incident-io-to-f1-api"
---

# Connect incident.io to F1 API

When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Find drivers by name** in [F1 API](https://apiant.ai/connections/f1-api). Describe the whole flow and it is built, tested on every scenario and kept running.

incident.io **1** trigger incident.io **10** actions F1 API **12** 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 F1 API 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 F1 API

- When **New Incident** in incident.io then **Find drivers by name** in F1 API
- When **New Incident** in incident.io then **Find teams by name** in F1 API

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 F1 API

## Triggers and actions 1 trigger · 22 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

**Find drivers by name**

Searches Formula 1 drivers by first name or surname and returns the matching drivers.

- Action

**Find teams by name**

Finds Formula 1 teams whose name matches the search text.

- Action

**Get driver**

Returns the details of one Formula 1 driver — name, nationality, birthday, racing number and short name.

- Action

**Get driver standings**

Returns the drivers' championship standings for a season, with each driver's position, points, wins and team.

- Action

**Get team**

Returns the details of a Formula 1 team, including its nationality, first appearance and championship counts.

- Action

**List circuits**

Returns all Formula 1 circuits, both active and historic, with location, length and lap record details.

- Action

**List drivers**

Returns all Formula 1 drivers in the database, both active and retired.

- Action

**List drivers by season**

Returns every Formula 1 driver who took part in the given season, with their team.

- Action

**List races by season**

Returns the races of a Formula 1 season, with schedule, circuit, winner and winning team for each race.

- Action

**List seasons**

Returns the Formula 1 World Championship seasons, with each season's year, name and Wikipedia link.

- Action

**List teams**

Returns all Formula 1 teams, active and historic, with their nationality and championship counts.

- Action

**List teams by season**

Returns the Formula 1 teams that competed in a given season.

## 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)
- [ **F1 API** Free F1 data in real time with his own NPM package](https://apiant.ai/connections/f1-api)

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 F1 API

- [ **Tally to F1 API** The simplest way to create beautiful forms and surveys, for free.](https://apiant.ai/connect/tally-to-f1-api)
- [ **HubSpot to F1 API** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-f1-api)
- [ **Salesforce to F1 API** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-f1-api)
- [ **Slack to F1 API** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-f1-api)
- [ **Google Sheets to F1 API** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-f1-api)
- [ **Gmail to F1 API** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-f1-api)

Questions

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

Any of F1 API's 12 actions, including Find drivers by name, Find teams by name, Get driver and Get driver standings. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from F1 API to incident.io?

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

###

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

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