--- title: "Connect incident.io and Leiga - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Create Issue\" in Leiga, or \"Updated Issue\" in Leiga to \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/incident-io-to-leiga" --- # Connect incident.io and Leiga When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Create Issue** in [Leiga](https://apiant.ai/connections/leiga), or **Updated Issue** in Leiga to **Find Users On-Call** in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Leiga **1** trigger Leiga **15** 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 Leiga 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 and Leiga can do together ### From incident.io to Leiga - When **New Incident** in incident.io then **Create Issue** in Leiga - When **New Incident** in incident.io then **Update issue** in Leiga ### From Leiga to incident.io - When **Updated Issue** in Leiga then **Find Users On-Call** in incident.io - When **Updated Issue** in Leiga 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 Leiga ## Triggers and actions 2 triggers · 25 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. - Trigger **Updated Issue** Triggers when an issue is updated in Leiga. - Action **Add comment** Adds a comment to a Leiga issue or other record, optionally as a reply to an existing comment. - Action **Add epic** Creates a new epic in a Leiga project. - Action **Add project** Creates a new project in Leiga from a project template, with a name, leader and optional description. - Action **Add version** Creates a new version (release) in Leiga with a name, owner, and optional description, start date and estimated release date. - Action **Create Issue** Creates a new issue in a Leiga project with the issue type and field values you provide. - Action **Delete issue** Deletes an issue from a Leiga project. - Action **Find issues by criteria** Searches the issues in a Leiga project matching a summary keyword, status types, field values or date ranges, and returns the matching issues. - Action **Get issue** Returns the full details of a Leiga issue, including its custom field values, by issue ID. - Action **Get project** Returns the details of a Leiga project by its ID. - Action **Get version** Returns the details of a Leiga version, including its name, status and release dates. - Action **List comments** Returns the comments on a Leiga issue or other item, including replies and attachments. - Action **List Issue Types** Returns the issue types (such as bug or task) available in a Leiga project. - Action **List projects** Returns all projects in your Leiga organization with their id, name, key and archived status. - Action **Update issue** Updates an existing Leiga issue's field values, such as its summary, description, status, priority, assignee or labels. - Action **Update project** Updates a Leiga project's overview fields, such as its name or start time. ## 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) - [ **Leiga** Offering powerful features and flexible solutions, Leiga empowers agile teams to work, collaborate, improve...](https://apiant.ai/connections/leiga) 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 Leiga - [ **HubSpot to Leiga** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-leiga) - [ **Google Sheets to Leiga** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-leiga) - [ **Gmail to Leiga** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-leiga) - [ **Google Calendar to Leiga** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-leiga) - [ **Google Drive to Leiga** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-leiga) - [ **ActiveCampaign to Leiga** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-leiga) Questions ## incident.io and Leiga, 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 Leiga when something happens in incident.io? Any of Leiga's 15 actions, including Create Issue, Update issue, Update project and Add comment. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Leiga to incident.io? Yes. When something happens in Leiga, your agent can act in incident.io too. This page covers both directions: Leiga's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Leiga? 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 Leiga 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.