Build solutions, not workarounds.
What do you want Cliniko and Omise to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Cliniko can start in Omise
When New cancelled attendee in Cliniko
then Add charge in Omise
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 Omise
Triggers and actions 17 triggers · 57 actions
- Cancelled individual appointment
Triggered when an individual appointment is cancelled.
- New cancelled attendee
Triggered when an attendee is cancelled.
- New or updated attendee
Triggered when an attendee is created or updated.
- New or updated business
Triggered when a business is created or updated.
- New or updated communication
Triggered when a communication is created or updated.
- New or updated contact
Triggered when a contact is created or updated.
- New or updated daily availability
Triggered when a daily availability is created or updated.
- New or updated group appointment
Triggered when a group appointment is created or updated.
- New or updated individual appointment
Triggered when an individual appointment is created or updated.
- New or updated invoice
Triggered when an invoice is created or updated.
- New or updated patient
Triggered when a patient is created or updated.
- New or updated patient case
Triggered when a patient case is created or updated.
- New or updated practitioner
Triggered when a practitioner is created or updated.
- New or updated treatment notes
Triggered when treatment notes is created or updated.
- 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.
- 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.
- 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.
- Archive patient
Archives a patient. An error will occur if the patient is not found.
- Create contact
Creates a new contact.
- Create patient
Creates a new patient.
- Find Appointment by Patient Id
Returns appointment details for the specified patient if the Patient ID exists.
- Find cancelled appointment
Searches for a cancelled appointment. If no matching appointment is found, an error occurs.
- Find contact by email
Returns details of the contact having the specified email address. An error occurs if zero or multiple are found.
- Find patient by email
Returns details of the patient having the specified email address. An error occurs if zero or multiple are found.
- Get appointment
Returns details of the specified appointment.
- Get appointments by practitioner ID
Returns appointment details by practitioner ID.
- Get appointment type
Returns details of the specified appointment type.
- Get appointment type billable item
Returns details for a billable item.
- Get billable item
Returns details of the specified billable item.
- Get business
Returns details of the specified business.
- Get cancelled appointment
Returns details of the specified cancelled appointment.
- Get contact
Returns details of the specified contact.
- Get group appointment
Returns details of the specified group appointment.
- Get group appointment attendees
Returns attendee information for the specified group appointment.
- Get individual appointment attendees
Returns attendee information for the specified individual appointment.
- Get invoice
Returns details of the specified invoice.
- Get patient
Returns details of the specified patient.
- Get patient case
Returns details of the specified patient case.
- Get patient referral source
Returns the referral source for the specified patient.
- Get practitioner
Returns details of the specified practitioner. An error occurs if not found.
- Get practitioner availabilities
Returns availability information for the specified practitioner.
- List invoices for patient case
Emits all invoice IDs for the specified patient case.
- 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.
- 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.
- Update contact
Updates a contact.
- Update patient
Updates a patient.
- Update patient custom field
Updates the value of the specified custom field for the specified patient.
- 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).
- Add charge
Create a charge for an amount/currency against a card, customer, or source.
- Add customer
Create a customer, optionally attaching a card via token.
- Add recipient
Creates a new transfer recipient (individual or corporation) with a destination bank account.
- Add refund
Create a refund on a captured charge.
- Add source
Creates a payment source (PromptPay, internet banking, mobile banking, Alipay, installments, TrueMoney and other non-card methods) that can then be charged with Add charge.
- Add token
Creates a single-use card token in Omise using the account's public key. Use the token to create one charge or to attach the card to a customer.
- Add transfer
Creates a transfer from your Omise balance to your own bank account or to a verified third-party recipient.
- Delete card
Permanently removes a saved card from an Omise customer.
- Delete customer
Destroy a customer.
- Delete recipient
Destroy a recipient.
- Get charge
Retrieves a single Omise charge by its ID.
- Get customer
Retrieve a customer by id.
- Get dispute
Retrieve a dispute by id.
- Get recipient
Retrieve a recipient by id.
- Get refund
Retrieve a refund by id.
- Get source
Retrieve a payment source by id.
- Get token
Retrieves a card token by its ID, including the card it represents and whether it has been used.
- Get transfer
Retrieves a single Omise transfer by its ID.
- List cards
Returns the list of cards saved on an Omise customer.
- List customers
List all customers.
- List recipients
List all recipients.
- List transfers
List all transfers.
- Update charge
Updates the description and/or metadata of an existing Omise charge.
- Update customer
Update a customer's details.
- Update dispute
Update a dispute's message/status.
- Update recipient
Update a recipient's details.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cliniko
Cliniko to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Cliniko to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Cliniko to SendGridSendGrid by Twilio — email delivery and marketing platform.
Cliniko to IntercomIntercom is a customer communications platform for support, engagement, and marketing.
Cliniko to FreshdeskFreshdesk is a cloud-based customer support and helpdesk platform.
Cliniko to KlaviyoKlaviyo is a marketing automation platform for email and SMS.
More into Omise
HubSpot to OmiseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to OmiseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to OmiseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to OmiseGoogle Sheets
Gmail to OmiseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OmiseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cliniko and Omise, 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 Omise when something happens in Cliniko?
Any of Omise's 26 actions, including Update charge, Update customer, Update dispute and Update recipient. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Omise to Cliniko?
Omise has no triggers in the catalog today, so automations start in Cliniko. If you need the other direction, ask: your agent reads Omise's API documentation and adds it.
Do I have to build a connector for Cliniko or Omise?
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.
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.