--- title: "Connect Commonsku and incident.io - APIANT.ai" description: "When \"New client\" fires in Commonsku, your agent runs \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/commonsku-to-incident-io" --- # Connect Commonsku and incident.io When **New client** fires in [Commonsku](https://apiant.ai/connections/commonsku), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Add client contact** in Commonsku. Describe the whole flow and it is built, tested on every scenario and kept running. Commonsku **3** triggers Commonsku **22** actions incident.io **1** trigger incident.io **11** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Commonsku 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 Commonsku and incident.io can do together ### From Commonsku to incident.io - When **New client** in Commonsku then **Find Users On-Call** in incident.io - When **New invoice** in Commonsku then **Add follow-up** in incident.io ### From incident.io to Commonsku - When **New Incident** in incident.io then **Add client contact** in Commonsku - When **New Incident** in incident.io then **Update contact** in Commonsku 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 Commonsku and incident.io ## Triggers and actions 4 triggers · 33 actions - Trigger **New client** Triggers when a new client is added in commonsku. - Trigger **New invoice** Triggers when a new invoice is created in commonsku. - Trigger **Sales Order Status Change** Triggers when a sales order reaches a new status, such as Client Approved, In Production or Shipped. Each newly created sales order also fires once with its first status. - Action **Add client** Creates a new client in commonsku. - Action **Add client address** Creates a new address in a client's address book and returns the created address. - Action **Add client contact** Creates a contact for a commonsku client and returns the new contact. - Action **Add project** Creates a new project for an existing client in commonsku. - Action **Add tag** Creates a tag in your commonsku company, or returns the existing tag if one with the same label already exists. - Action **Delete client** Deletes a client from commonsku by ID, along with all of its contacts and addresses, and returns the deleted client. - Action **Find products by keyword** Returns the products whose name, supplier code or tag match a keyword, optionally narrowed by supplier, division, tag, owner or net price. - Action **Get client** Returns the details of a single Commonsku client, including its terms, industry, status and tags. An error occurs if the client is not found. - Action **Get invoice** Returns a single invoice, including its customer, billing and shipping details, line items and totals. An error occurs if the invoice is not found. - Action **Get product** Returns the full details of a single product by its ID, including its colors, sizes, imprints, images, SKUs, costs and prices. An error occurs if the product is not found. - Action **Get project** Returns the details of a single commonsku project by its ID. - Action **List client contacts** Returns the contacts associated with a commonsku client, including names, email, department and phone numbers. - Action **List clients** Returns the clients in your commonsku account, optionally filtered by customer number, client name, credit hold status or last-updated date. - Action **List invoices** Returns invoices in your commonsku account, optionally filtered by status, customer, numbers or dates. - Action **List products** Returns products in your commonsku account, optionally filtered by keyword, supplier, division, tag or price, or by a special mode such as popular or recently used products. - Action **List projects** Returns the projects in your commonsku account, optionally filtered by client, dates or project number. - Action **List purchase orders** Returns the purchase orders in your commonsku account, optionally filtered by status, client, order numbers, dates or tracking number. - Action **List sales orders** Returns the sales orders in your commonsku account, optionally filtered by status, client, numbers and date ranges. - Action **List tags** Returns the tags defined in your commonsku company, optionally limited to one record, one record type, or a label search. - Action **Update client** Updates an existing commonsku client's name, payment terms, industry, rep, website, status, credit hold and tags. - Action **Update contact** Updates an existing client contact's name, email or department in commonsku. - Action **Update product** Updates an existing product in commonsku. Only the fields you fill in are changed. - 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 **Update incident** Edits an existing incident's name, summary, severity, status, call link, Slack channel name, custom fields, role assignments or timestamps. Only the values you provide are changed. ## Each app on its own - [ **Commonsku** commonsku is a workflow management, CRM, and ERP platform specifically designed for the promotional goods...](https://apiant.ai/connections/commonsku) - [ **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 Commonsku - [ **Commonsku to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/commonsku-to-hubspot) - [ **Commonsku to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/commonsku-to-salesforce) - [ **Commonsku to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/commonsku-to-slack) - [ **Commonsku to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/commonsku-to-google-sheets) - [ **Commonsku to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/commonsku-to-gmail) - [ **Commonsku to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/commonsku-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 ## Commonsku and incident.io, answered ### ### What can start an automation from Commonsku? Any of Commonsku's 3 triggers in the catalog, including New client, New invoice and Sales Order Status Change. 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 Commonsku? Any of incident.io's 11 actions, including Create Incident, Update incident, Add follow-up and Add incident update. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from incident.io to Commonsku? Yes. When something happens in incident.io, your agent can act in Commonsku too. This page covers both directions: incident.io's triggers and Commonsku's actions are listed here as well. ### ### Do I have to build a connector for Commonsku 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 Commonsku 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.