Integration
Connect incident.io and KrispCall
When New Incident fires in incident.io, your agent runs Update Contact in KrispCall, or New Contact in KrispCall 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 KrispCall 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 KrispCall can do together
From incident.io to KrispCall
When New Incident in incident.io
then Update Contact in KrispCall
When New Incident in incident.io
then Get Blocked Contact in KrispCall
From KrispCall to incident.io
When New Contact in KrispCall
then Find Users On-Call in incident.io
When New SMS_MMS in KrispCall
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 KrispCall
Triggers and actions 5 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
Call EventTriggers when a call happens between a contact's number and one of your KrispCall numbers.
Trigger
New ContactTriggers when a contact is added to your KrispCall workspace.
Trigger
New SMS_MMSTriggers when a text or picture message arrives on one of your KrispCall numbers.
Trigger
New SMS/MMS SentTriggers when a text or picture message is sent from one of your KrispCall numbers.
Action
Delete ContactsDeletes one contact from your KrispCall workspace.
Action
Get Blocked ContactReturns one blocked KrispCall contact.
Action
Get CallReturns one KrispCall call by its ID.
Action
Get ContactReturns one KrispCall contact by its ID.
Action
Get Contact Do Not DisturbReturns one contact's Do Not Disturb setting.
Action
Get MemberReturns one KrispCall workspace member.
Action
Get NumberReturns one of your KrispCall phone numbers.
Action
Get SMSReturns one KrispCall text message by its ID.
Action
Get WorkspaceReturns your KrispCall workspace's details.
Action
List Blocked ContactsReturns the contacts blocked in your KrispCall workspace.
Action
List CallsReturns calls between a contact's number and one of your KrispCall numbers.
Action
List ContactsReturns the contacts in your KrispCall workspace, one page at a time.
Action
List Do Not Disturb ContactsReturns contacts that have Do Not Disturb turned on.
Action
List MembersReturns the members of your KrispCall workspace.
Action
List NumbersReturns the phone numbers in your KrispCall workspace.
Action
List SMSReturns text messages between a contact's number and one of your KrispCall numbers.
Action
Send MMSSends a picture or file message from one of your KrispCall numbers.
Action
Send SMSSends a text message from one of your KrispCall numbers.
Action
Update ContactUpdates an existing KrispCall contact; only the fields you supply change.
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 KrispCall
HubSpot to KrispCallHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to KrispCallGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KrispCallGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to KrispCallGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to KrispCallGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to KrispCallActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
incident.io and KrispCall, 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 KrispCall when something happens in incident.io?
Any of KrispCall's 19 actions, including Send MMS, Send SMS, Update Contact and Get Blocked Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from KrispCall to incident.io?
Yes. When something happens in KrispCall, your agent can act in incident.io too. This page covers both directions: KrispCall's triggers and incident.io's actions are listed here as well.
Do I have to build a connector for incident.io or KrispCall?
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 KrispCall 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.