--- title: "Connect incident.io to Livestorm - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Create Event\" in Livestorm." canonical: "https://apiant.ai/connect/incident-io-to-livestorm" --- # Connect incident.io to Livestorm When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Create Event** in [Livestorm](https://apiant.ai/connections/livestorm). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **11** actions Livestorm **16** 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 Livestorm 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 Livestorm - When **New Incident** in incident.io then **Create Event** in Livestorm - When **New Incident** in incident.io then **Update Event** in Livestorm 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 Livestorm ## Triggers and actions 1 trigger · 27 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 **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. - Action **Create Event** Creates a new Livestorm event with its first session, either from scratch or by duplicating the settings of an existing event. - Action **Create Registrant** Registers a person for an upcoming Livestorm event session, with their email, name, registration fields and UTM tracking data. - Action **Create Session** Schedules a new session for an existing Livestorm event. Returns the created session, including its room link, status and scheduled start time. - Action **Find People** Finds people in your Livestorm workspace by email address, optionally limited to participants or team members. - Action **Find Session** Finds event sessions in your Livestorm workspace whose name matches the one you give, optionally narrowed by status and date range. Returns the matching sessions and the first match. - Action **Get event** Returns a single Livestorm event, including its title, status, registration link, settings, owner and registration fields. - Action **Get person** Returns the details of a person in your Livestorm workspace, such as their name, email, role and timezone. - Action **Get session** Returns a single Livestorm session, including its status, schedule, room link and attendee counts, optionally with its event, people, chat messages, questions or recordings. - Action **List events** Returns the events in your Livestorm workspace, optionally filtered by title, scheduling status, tag, or creation and update dates. - Action **List session questions** Returns all the questions attendees asked during a Livestorm session, with any answers given. - Action **List sessions** Returns the sessions across all events in your Livestorm workspace, optionally filtered by status, scheduled start date, creation date or last update date. - Action **Remove Event** Deletes a single Livestorm event. - Action **Remove Registrant** Removes a registrant from a Livestorm event session, cancelling their registration. - Action **Remove Session** Deletes a single Livestorm event session. - Action **Update Event** Updates an existing Livestorm event, changing only the details you fill in, such as its title, description, status or room settings. - Action **Update Session** Updates a Livestorm session's name, start date/time or timezone. Fields left blank keep their current values. ## 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) - [ **Livestorm** Livestorm is an end-to-end engagement platform that enables you to connect, engage, and capture actionable...](https://apiant.ai/connections/livestorm) 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 Livestorm - [ **HubSpot to Livestorm** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-livestorm) - [ **Salesforce to Livestorm** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-livestorm) - [ **Slack to Livestorm** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-livestorm) - [ **Google Sheets to Livestorm** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-livestorm) - [ **Gmail to Livestorm** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-livestorm) - [ **Google Calendar to Livestorm** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-livestorm) Questions ## incident.io and Livestorm, 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 Livestorm when something happens in incident.io? Any of Livestorm's 16 actions, including Create Event, Create Registrant, Create Session and Update Event. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Livestorm to incident.io? Livestorm has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Livestorm's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Livestorm? 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 Livestorm 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.