--- title: "Connect COR and incident.io - APIANT.ai" description: "When \"Create Brand\" fires in COR, your agent runs \"Find Users On-Call\" in incident.io, or \"New Incident\" in incident.io to \"Create Invoice\" in COR." canonical: "https://apiant.ai/connect/cor-to-incident-io" --- # Connect COR and incident.io When **Create Brand** fires in [COR](https://apiant.ai/connections/cor), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Create Invoice** in COR. Describe the whole flow and it is built, tested on every scenario and kept running. COR **12** triggers COR **24** 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 COR 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 COR and incident.io can do together ### From COR to incident.io - When **Create Brand** in COR then **Find Users On-Call** in incident.io - When **Create Client** in COR then **Add follow-up** in incident.io ### From incident.io to COR - When **New Incident** in incident.io then **Create Invoice** in COR - When **New Incident** in incident.io then **Create Task** in COR 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 COR and incident.io ## Triggers and actions 13 triggers · 34 actions - Trigger **Create Brand** Triggers when a new brand is created in COR. - Trigger **Create Client** Triggers when a new client is created in COR. - Trigger **Create Hour** Triggers when a new time entry is logged in COR. - Trigger **Create Invoice** Triggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart. - Trigger **Create Product** Triggers when a new product is created in COR. - Trigger **Create Project** Triggers when a new project is created in COR. - Trigger **Create Task** Triggers when a new task is created in COR. Returns the new task's details. - Trigger **Create User** Triggers when a new user is created in COR. - Trigger **Updated Client** Triggers when an existing client is changed in COR. - Trigger **Updated Project** Triggers when an existing project is updated in COR. - Trigger **Updated Task** Triggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears. - Trigger **Updated User** Triggers when a user in COR is created or changed, such as their name, email, role, position or labels. - Action **Add brand** Creates a new brand under a client in COR. - Action **Add team** Creates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created. - Action **Create Client** Creates a new client in COR with its company details and primary contact, and returns the new client's id. - Action **Create Fee** Creates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee. - Action **Create Hour** Logs a time entry against a task in COR and returns the new entry's id. - Action **Create Invoice** Creates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction. - Action **Create Project** Creates a new project for a client in COR and returns the created project. - Action **Create Task** Creates a new task in COR, optionally within a project, and returns the created task. - Action **Delete Project** Deletes a project in COR by its ID. - Action **Delete task** Deletes a task in COR by its ID. - Action **Find clients by name** Returns the clients whose name matches the specified name. - Action **Find projects by name** Returns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details. - Action **Get client** Returns a single COR client by its id, including its business name, contact details, website and description. - Action **Get project** Returns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found. - Action **Get task** Returns a single COR task by its id, including its title, project, deadline, status and priority. - Action **List clients** Returns all clients in the COR account, optionally narrowed by filter criteria. - Action **List fees** Returns the fees in the COR account, including each fee's name, estimate, status and dates. - Action **List hours** Returns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose. - Action **List products** Returns all products in the COR account, each with its name, client and brand. - Action **List projects** Returns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state. - Action **List tasks** Returns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose. - Action **List teams** Returns the teams in the COR workspace, including each team's name and description. - Action **Update Project** Updates an existing project in COR, changing only the fields you fill in, and returns the updated project. - Action **Update Task** Updates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task. - 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 - [ **COR** COR is the all-in-one management solution for creative agencies that automate timesheets, through AI, to...](https://apiant.ai/connections/cor) - [ **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 COR - [ **COR to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/cor-to-hubspot) - [ **COR to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/cor-to-salesforce) - [ **COR to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/cor-to-slack) - [ **COR to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/cor-to-google-sheets) - [ **COR to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/cor-to-gmail) - [ **COR to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/cor-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 ## COR and incident.io, answered ### ### What can start an automation from COR? Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create Invoice. 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 COR? 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 COR? Yes. When something happens in incident.io, your agent can act in COR too. This page covers both directions: incident.io's triggers and COR's actions are listed here as well. ### ### Do I have to build a connector for COR 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 COR 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.