--- title: "Connect Corymbus and incident.io - APIANT.ai" description: "When \"New Activity\" fires in Corymbus, your agent runs \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/corymbus-to-incident-io" --- # Connect Corymbus and incident.io When **New Activity** fires in [Corymbus](https://apiant.ai/connections/corymbus), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Create Contact** in Corymbus. Describe the whole flow and it is built, tested on every scenario and kept running. Corymbus **2** triggers Corymbus **9** actions incident.io **1** trigger incident.io **10** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Corymbus and incident.io 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 Corymbus and incident.io can do together ### From Corymbus to incident.io - When **New Activity** in Corymbus then **Find Users On-Call** in incident.io - When **New Contact** in Corymbus then **Add follow-up** in incident.io ### From incident.io to Corymbus - When **New Incident** in incident.io then **Create Contact** in Corymbus - When **New Incident** in incident.io then **Find contacts** in Corymbus 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 Corymbus and incident.io ## Triggers and actions 3 triggers · 19 actions - Trigger **New Activity** Triggers when a new activity is created in Corymbus, optionally limited to activities linked to a given account, contact or opportunity, or owned by a given user. - Trigger **New Contact** Triggers when a new contact is created in Corymbus, optionally limited to contacts matching a name, account, activity, opportunity, group or owner. - Action **Add activity** Creates a new activity (task, call, meeting, note or email) in Corymbus and returns the created activity. - Action **Connect entities** Connects two Corymbus records together, for example an opportunity to an activity or a contact to an account. - Action **Create Account** Creates a new account (company) in Corymbus CRM and returns the created account. - Action **Create Contact** Creates a new contact (person) in Corymbus, optionally linked to an account, and returns the created contact. - Action **Create Opportunity** Creates a new opportunity (deal) in Corymbus, optionally linked to an account, with an amount, status and expected close date. - Action **Find Account** Finds accounts whose name contains the given text, optionally limited to an owner or a connected activity, and returns the matches. - Action **Find activities** Returns the activities whose name contains the text you give, optionally narrowed to an account, contact, opportunity, owner or late activities. - Action **Find contacts** Returns the Corymbus contacts whose first or last name contains the text you give, optionally narrowed by account, activity, opportunity, group or owner. - Action **Find opportunities** Returns the opportunities whose name contains the text you specify, optionally narrowed by account, contact, activity, owner or expected close period. - 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. ## Each app on its own - [ **Corymbus** Corymbus is a CRM platform devoted to small businesses and freelances.](https://apiant.ai/connections/corymbus) - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) Reviews ## What our customers say ## More from Corymbus - [ **Corymbus to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/corymbus-to-hubspot) - [ **Corymbus to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/corymbus-to-salesforce) - [ **Corymbus to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/corymbus-to-slack) - [ **Corymbus to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/corymbus-to-google-sheets) - [ **Corymbus to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/corymbus-to-gmail) - [ **Corymbus to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/corymbus-to-google-calendar) ## More into incident.io - [ **HubSpot to incident.io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-incident-io) - [ **Google Sheets to incident.io** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-incident-io) - [ **Gmail to incident.io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-incident-io) - [ **Google Calendar to incident.io** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-incident-io) - [ **Google Drive to incident.io** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-incident-io) - [ **ActiveCampaign to incident.io** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-incident-io) Questions ## Corymbus and incident.io, answered ### ### What can start an automation from Corymbus? Any of Corymbus's 2 triggers in the catalog, including New Activity and New Contact. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in incident.io when something happens in Corymbus? Any of incident.io's 10 actions, including Create Incident, Add follow-up, Add incident update and Find Users On-Call. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from incident.io to Corymbus? Yes. When something happens in incident.io, your agent can act in Corymbus too. This page covers both directions: incident.io's triggers and Corymbus's actions are listed here as well. ### ### Do I have to build a connector for Corymbus or incident.io? 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 Corymbus and incident.io 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.