--- title: "Connect incident.io and Pleo - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add account\" in Pleo, or \"New Employee\" in Pleo to \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/incident-io-to-pleo" --- # Connect incident.io and Pleo When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add account** in [Pleo](https://apiant.ai/connections/pleo), or **New Employee** in Pleo 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 Pleo **2** triggers Pleo **24** 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 Pleo 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 Pleo can do together ### From incident.io to Pleo - When **New Incident** in incident.io then **Add account** in Pleo - When **New Incident** in incident.io then **Add tag group** in Pleo ### From Pleo to incident.io - When **New Employee** in Pleo then **Find Users On-Call** in incident.io - When **New Tag** in Pleo 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 Pleo ## Triggers and actions 3 triggers · 34 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 **New Employee** Triggered when a new employee is added in Pleo. - Trigger **New Tag** Triggers when a new tag is added to the selected tag group. - Action **Add account** Creates an account in a Pleo company's chart of accounts, matching a record in your accounting system, and returns the new account. - Action **Add tag group** Creates a new tag group (a cost-centre dimension such as Projects or Departments) in Pleo. - Action **Add tax code** Creates a tax code in a Pleo company, with its name, rate and type. - Action **Add team** Creates a new team in a Pleo company or organisation and returns the created team. - Action **Create Tag** Creates a new tag in a Pleo tag group, such as a cost centre or project, and returns the created tag. - Action **Delete tag** Deletes a tag from Pleo by its ID. - Action **Delete tag group** Deletes a tag group from Pleo by its ID. - Action **Delete tax code** Deletes a tax code from a Pleo company. - Action **Get an Employee** Returns one Pleo employee by ID, including their name, email, job title, phone, role, company and avatar. - Action **Get company balance** Returns the current balance of every Pleo account belonging to a company, including available funds, pending debits and overdraft. - Action **Get Expense** Returns a single Pleo expense (accounting entry) by its ID, including its amounts, merchant, category, tags, review and export status, and receipt IDs. - Action **Get tag** Returns a Pleo tag by its ID, including its name, code, tag group and archived status. - Action **Get tag group** Returns a tag group by its ID, including its name, code, archived status, metadata and total number of tags. - Action **Get Tax Code** Returns a single tax code from Pleo, including its name, rate, type and archived status. - Action **Get team** Returns a Pleo team by its ID, including its name, code, company, organisation and employee IDs. An error occurs if the team is not found. - Action **List accounts** Returns the accounts in a Pleo company's chart of accounts, optionally narrowed by name, code, external ID, account ID or archived status. - Action **List employees** Returns the employees in your Pleo company, optionally filtered by company, email or external ID. - Action **List tag groups** Returns the tag groups for a Pleo company, or for all companies in an organisation. - Action **List tags** Returns the tags in a Pleo tag group, optionally including archived tags. - Action **List tax codes** Returns the tax codes for a Pleo company, optionally filtered by code, type, archived status or specific tax code IDs. - Action **List teams** Returns the teams in a Pleo company or organisation, optionally filtered by name, member employee or team. - Action **Update tag** Updates a tag's code, name, archived state and additional dimension values in Pleo, and returns the updated tag. - Action **Update tag group** Updates a tag group's name, code, archived status and metadata. All values replace the tag group's current ones. - Action **Update tax code** Updates an existing tax code in Pleo, including its name, rate, type and archived status, and returns the updated tax code. ## 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) - [ **Pleo** Pleo offers smart company cards that automate expense reports and simplify company spending.](https://apiant.ai/connections/pleo) 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 Pleo - [ **HubSpot to Pleo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-pleo) - [ **Google Sheets to Pleo** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-pleo) - [ **Gmail to Pleo** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-pleo) - [ **Google Calendar to Pleo** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-pleo) - [ **Google Drive to Pleo** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-pleo) - [ **Mailchimp to Pleo** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-pleo) Questions ## incident.io and Pleo, 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 Pleo when something happens in incident.io? Any of Pleo's 24 actions, including Create Tag, Update tag, Update tag group and Update tax code. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Pleo to incident.io? Yes. When something happens in Pleo, your agent can act in incident.io too. This page covers both directions: Pleo's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Pleo? 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 Pleo 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.