--- title: "Connect Cliniko and incident.io - APIANT.ai" description: "When \"New or updated attendee\" fires in Cliniko, your agent runs \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/cliniko-to-incident-io" --- # Connect Cliniko and incident.io When **New or updated attendee** fires in [Cliniko](https://apiant.ai/connections/cliniko), 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 Cliniko. Describe the whole flow and it is built, tested on every scenario and kept running. Cliniko **17** triggers Cliniko **36** 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 Cliniko 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 Cliniko and incident.io can do together ### From Cliniko to incident.io - When **New or updated attendee** in Cliniko then **Find Users On-Call** in incident.io - When **New or updated business** in Cliniko then **Add follow-up** in incident.io ### From incident.io to Cliniko - When **New Incident** in incident.io then **Create contact** in Cliniko - When **New Incident** in incident.io then **Update contact** in Cliniko 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 Cliniko and incident.io ## Triggers and actions 18 triggers · 46 actions - Trigger **Cancelled individual appointment** Triggered when an individual appointment is cancelled. - Trigger **New cancelled attendee** Triggered when an attendee is cancelled. - Trigger **New or updated attendee** Triggered when an attendee is created or updated. - Trigger **New or updated business** Triggered when a business is created or updated. - Trigger **New or updated communication** Triggered when a communication is created or updated. - Trigger **New or updated contact** Triggered when a contact is created or updated. - Trigger **New or updated daily availability** Triggered when a daily availability is created or updated. - Trigger **New or updated group appointment** Triggered when a group appointment is created or updated. - Trigger **New or updated individual appointment** Triggered when an individual appointment is created or updated. - Trigger **New or updated invoice** Triggered when an invoice is created or updated. - Trigger **New or updated patient** Triggered when a patient is created or updated. - Trigger **New or updated patient case** Triggered when a patient case is created or updated. - Trigger **New or updated practitioner** Triggered when a practitioner is created or updated. - Trigger **New or updated treatment notes** Triggered when treatment notes is created or updated. - Trigger **Patient added or removed for group appointment in date range** Triggered when a patient is added or removed for a group appointment within the specified date range. - Trigger **Two-way sync new or updated contacts** A trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Trigger **Two-way sync new or updated patients** A trigger for two-way syncing new and updated patients, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Action **Archive patient** Archives a patient. An error will occur if the patient is not found. - Action **Create contact** Creates a new contact. - Action **Create patient** Creates a new patient. - Action **Find Appointment by Patient Id** Returns appointment details for the specified patient if the Patient ID exists. - Action **Find cancelled appointment** Searches for a cancelled appointment. If no matching appointment is found, an error occurs. - Action **Find contact by email** Returns details of the contact having the specified email address. An error occurs if zero or multiple are found. - Action **Find patient by email** Returns details of the patient having the specified email address. An error occurs if zero or multiple are found. - Action **Find Patient by Email and Date of Birth** Finds the single active patient whose email and date of birth both match, returning the patient ID and the match count. - Action **Get appointment** Returns details of the specified appointment. - Action **Get appointments by practitioner ID** Returns appointment details by practitioner ID. - Action **Get appointment type** Returns details of the specified appointment type. - Action **Get appointment type billable item** Returns details for a billable item. - Action **Get billable item** Returns details of the specified billable item. - Action **Get business** Returns details of the specified business. - Action **Get cancelled appointment** Returns details of the specified cancelled appointment. - Action **Get contact** Returns details of the specified contact. - Action **Get group appointment** Returns details of the specified group appointment. - Action **Get group appointment attendees** Returns attendee information for the specified group appointment. - Action **Get individual appointment attendees** Returns attendee information for the specified individual appointment. - Action **Get invoice** Returns details of the specified invoice. - Action **Get patient** Returns details of the specified patient. - Action **Get patient attachment** Returns a patient attachment from Cliniko, including its filename, file type and description. - Action **Get patient case** Returns details of the specified patient case. - Action **Get patient referral source** Returns the referral source for the specified patient. - Action **Get practitioner** Returns details of the specified practitioner. An error occurs if not found. - Action **Get practitioner availabilities** Returns availability information for the specified practitioner. - Action **List Appointments in Date Range** Returns every individual appointment that starts within a given time window, with the total count. - Action **List invoices for patient case** Emits all invoice IDs for the specified patient case. - Action **List Patients** Returns Cliniko patients, optionally filtered (e.g. updated after a date) and sorted, with the total count. - Action **Two-way sync add or update a contact** An action for two-way syncing new and updated contacts, with enhanced on-the-fly mapping using contact email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping. - Action **Two-way sync add or update a patient** An action for two-way syncing new and updated patients, with enhanced on-the-fly mapping using patient email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping. - Action **Update contact** Updates a contact. - Action **Update patient** Updates a patient. - Action **Update patient custom field** Updates the value of the specified custom field for the specified patient. - Action **Update patient referral** Sets or changes a patient's referral source. Choose the referral source type; supply a Referrer ID only for types that take one (e.g. Patient or Contact). - Action **Upload patient attachment** Uploads a file, such as a PDF, to a patient's record in Cliniko as an attachment. - 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 - [ **Cliniko** Cliniko is a practice management platform — manage patients, appointments, invoices, contacts, and...](https://apiant.ai/connections/cliniko) - [ **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 Cliniko - [ **Cliniko to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/cliniko-to-jira) - [ **Cliniko to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/cliniko-to-zoom) - [ **Cliniko to SendGrid** SendGrid by Twilio — email delivery and marketing platform.](https://apiant.ai/connect/cliniko-to-sendgrid) - [ **Cliniko to Intercom** Intercom is a customer communications platform for support, engagement, and marketing.](https://apiant.ai/connect/cliniko-to-intercom) - [ **Cliniko to Freshdesk** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/cliniko-to-freshdesk) - [ **Cliniko to Klaviyo** Klaviyo is a marketing automation platform for email and SMS.](https://apiant.ai/connect/cliniko-to-klaviyo) ## 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 ## Cliniko and incident.io, answered ### ### What can start an automation from Cliniko? Any of Cliniko's 17 triggers in the catalog, including New cancelled attendee, New or updated attendee, New or updated business and New or updated communication. 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 Cliniko? 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 Cliniko? Yes. When something happens in incident.io, your agent can act in Cliniko too. This page covers both directions: incident.io's triggers and Cliniko's actions are listed here as well. ### ### Do I have to build a connector for Cliniko 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 Cliniko 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.