Integration
Connect incident.io and InsurGrid
When New Incident fires in incident.io, your agent runs Create Form in InsurGrid, or New Form in InsurGrid to Find Users On-Call in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want incident.io and InsurGrid to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What incident.io and InsurGrid can do together
From incident.io to InsurGrid
When New Incident in incident.io
then Create Form in InsurGrid
When New Incident in incident.io
then Create Loss Run Request in InsurGrid
From InsurGrid to incident.io
When New Form in InsurGrid
then Find Users On-Call in incident.io
When New Loss Run Request in InsurGrid
then Add follow-up in incident.io
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 InsurGrid
Triggers and actions 3 triggers · 31 actions
Trigger
New IncidentTriggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode.
Action
Add follow-upCreates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels.
Action
Add incident updateShares an update on an incident: a message, a move to a new status, a new severity, or any combination.
Action
Create IncidentCreates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields.
Action
Find Users On-CallFinds 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 incidentReturns a single incident, including its status, severity, role assignments, timestamps and custom field values.
Action
Get ScheduleReturns a single on-call schedule, including its rotations, time zone and current shifts.
Action
List actionsReturns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date.
Action
List incidentsReturns incidents in your incident.io account, optionally filtered by status, severity, type, mode and created/updated dates.
Action
List schedulesReturns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift.
Action
List severitiesReturns every incident severity configured for your incident.io organisation.
Action
List usersReturns the users in your incident.io account, optionally filtered by email address or Slack user ID.
Action
Update incidentEdits 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.
Trigger
New FormTriggers when a new intake form is created.
Trigger
New Loss Run RequestTriggers when a new loss run request is created.
Action
Archive FormArchives an intake form so it stops taking submissions.
Action
Authorize Loss Run RequestSends a loss run request out for the insured's signature.
Action
Create FormCreates a new intake form.
Action
Create Loss Run RequestCreates a loss run request for an insured and one carrier policy.
Action
Delete FormDeletes an intake form.
Action
Duplicate FormCreates a copy of an intake form.
Action
Get FormReturns one intake form with its steps and questions.
Action
Get Loss Run Document Download LinkReturns a temporary download link for a received loss run document.
Action
Get Loss Run RequestReturns one loss run request with its insured, signer and policies.
Action
Get Policy ComparisonReturns the status and result of a policy comparison.
Action
Get Policy ExtractionReturns the status and structured data of a policy extraction.
Action
List CarriersReturns the insurance carriers you can request loss runs from.
Action
List Coverage TypesReturns the coverage types a loss run request can name.
Action
List FormsReturns the intake forms in your InsurGrid account, optionally only those belonging to one of your users.
Action
List Loss Run RequestsReturns your loss run requests, optionally filtered by status or search text.
Action
List Signer TitlesReturns the titles an authorized signer can hold.
Action
Publish FormPublishes an intake form so customers can fill it in.
Action
Reactivate FormReactivates an archived intake form.
Action
Update FormUpdates an intake form's name, insurance line or redirect page.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from incident.io
incident.io to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
incident.io to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
incident.io to MailchimpMailchimp marketing automation and email platform.
incident.io to StripeStripe is a payment processing platform for online businesses.
incident.io to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
incident.io to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into InsurGrid
HubSpot to InsurGridHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to InsurGridGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to InsurGridGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InsurGridGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to InsurGridGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to InsurGridActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
incident.io and InsurGrid, 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 InsurGrid when something happens in incident.io?
Any of InsurGrid's 19 actions, including Create Form, Create Loss Run Request, Update Form and Authorize Loss Run Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from InsurGrid to incident.io?
Yes. When something happens in InsurGrid, your agent can act in incident.io too. This page covers both directions: InsurGrid's triggers and incident.io's actions are listed here as well.
Do I have to build a connector for incident.io or InsurGrid?
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 InsurGrid 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.