--- title: "Connect incident.io to Hamsa - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add knowledge base item\" in Hamsa." canonical: "https://apiant.ai/connect/incident-io-to-hamsa" --- # Connect incident.io to Hamsa When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add knowledge base item** in [Hamsa](https://apiant.ai/connections/hamsa). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Hamsa **21** 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 Hamsa 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 Hamsa - When **New Incident** in incident.io then **Add knowledge base item** in Hamsa - When **New Incident** in incident.io then **Add phone number** in Hamsa 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 Hamsa ## Triggers and actions 1 trigger · 31 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 **Add knowledge base item** Create a new knowledge base item for a voice agent. - Action **Add phone number** Add a phone number for a user. - Action **Add transcription job** Create a new asynchronous job (e.g. transcription). - Action **Add TTS voice** Create a new text-to-speech voice. - Action **Add voice agent** Create a new AI voice agent. - Action **Assign phone number** Assign a phone number to a voice agent. - Action **Delete knowledge base item** Delete a knowledge base item by ID. - Action **Delete phone number** Delete a phone number. - Action **Delete TTS voice** Delete a text-to-speech voice by ID. - Action **Get campaign** Get a campaign by ID. - Action **Get conversation** Get a call conversation record by ID. - Action **Get job** Get a single job's details by ID. - Action **Get voice agent** Retrieve a specific voice agent by ID. - Action **Initiate voice agent call** Initiate an outbound call with a voice agent via Twilio. - Action **List jobs** List jobs. - Action **List knowledge base items** Return a list of knowledge base items. - Action **List phone numbers** Return a list of phone numbers for a user. - Action **List TTS voices** Retrieve the list of available TTS voices. - Action **List voice agents** Retrieve a list of the account's voice agents. - Action **Transcribe audio** Generate a speech-to-text transcription from audio (not streamed). - Action **Update voice agent** Update an existing voice agent's configuration. ## 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) - [ **Hamsa** AI voice agent platform with lifelike avatars, RAG-powered conversations, and API/SDK for calls, CRM, and...](https://apiant.ai/connections/hamsa) 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 Hamsa - [ **MySQL to Hamsa** Connect directly to a MySQL database and run SQL statements from your automations.](https://apiant.ai/connect/mysql-to-hamsa) - [ **TimelinesAI to Hamsa** TimelinesAI allows you to share access to your personal or business Whatsapp account, integrate it with...](https://apiant.ai/connect/timelinesai-to-hamsa) - [ **HubSpot to Hamsa** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-hamsa) - [ **Salesforce to Hamsa** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-hamsa) - [ **Slack to Hamsa** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-hamsa) - [ **Google Sheets to Hamsa** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-hamsa) Questions ## incident.io and Hamsa, 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 Hamsa when something happens in incident.io? Any of Hamsa's 21 actions, including Update voice agent, Add knowledge base item, Add phone number and Add transcription job. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Hamsa to incident.io? Hamsa has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Hamsa's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Hamsa? 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 Hamsa 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.