--- title: "Connect incident.io to Pylon - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add internal note to issue\" in Pylon." canonical: "https://apiant.ai/connect/incident-io-to-pylon" --- # Connect incident.io to Pylon When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add internal note to issue** in [Pylon](https://apiant.ai/connections/pylon). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Pylon **25** 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 Pylon 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 Pylon - When **New Incident** in incident.io then **Add internal note to issue** in Pylon - When **New Incident** in incident.io then **Add task** in Pylon 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 Pylon ## Triggers and actions 1 trigger · 35 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 internal note to issue** Adds an internal note to a Pylon issue. Internal notes are not visible to the requester. - Action **Add tag** Creates a new tag in Pylon that can be applied to accounts, articles or issues. - Action **Add task** Creates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task. - Action **Create Account** Creates a new customer account in Pylon with its name, domains, owner, tags and other details. - Action **Create Account Activity** Creates a custom activity on a Pylon account's timeline. - Action **Create Call Recording** Creates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon. - Action **Delete account** Permanently deletes a Pylon account by its ID or external ID. - Action **Delete issue** Permanently deletes an issue in Pylon. - Action **Find Account by Name** Finds Pylon accounts by name, by exact or partial match, returning the matching accounts. - Action **Find contacts by criteria** Returns the contacts that match the specified search text and/or filter. - Action **Find issues by criteria** Returns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates. - Action **Get account** Returns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields. - Action **Get contact** Returns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID. - Action **Get issue** Returns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found. - Action **Get user** Returns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles. - Action **Get Users** Returns the users in your Pylon organization, optionally including deactivated users. - Action **List accounts** Returns all accounts in your Pylon organization, including their domains, owner, tags and custom field values. - Action **List contacts** Returns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values. - Action **List tags** Returns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to. - Action **List teams** Returns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule. - Action **Reply to issue** Sends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue. - Action **Update Account** Updates an existing Pylon account. Only the fields you fill in are changed. - Action **Update contact** Updates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed. - Action **Update issue** Updates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed. - Action **Update Issue Followers** Adds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers. ## 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) - [ **Pylon** Pylon is a modern, powerful support system built for B2B.](https://apiant.ai/connections/pylon) 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 Pylon - [ **HubSpot to Pylon** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-pylon) - [ **Salesforce to Pylon** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-pylon) - [ **Slack to Pylon** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-pylon) - [ **Google Sheets to Pylon** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-pylon) - [ **Gmail to Pylon** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-pylon) - [ **Google Calendar to Pylon** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-pylon) Questions ## incident.io and Pylon, 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 Pylon when something happens in incident.io? Any of Pylon's 25 actions, including Create Account, Create Account Activity, Create Call Recording and Update Account. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Pylon to incident.io? Pylon has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Pylon? 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 Pylon 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.