Integration
Connect Cliniko to Fullstory
When New or updated attendee fires in Cliniko, your agent runs Add user in Fullstory. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cliniko and Fullstory to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 Fullstory
When New or updated attendee in Cliniko
then Add user in Fullstory
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 Fullstory
Triggers and actions 17 triggers · 43 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.
- 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.
- 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 attachment
Returns a patient attachment from Cliniko, including its filename, file type and description.
- 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 Appointments in Date Range
Returns every individual appointment that starts within a given time window, with the total count.
- List invoices for patient case
Emits all invoice IDs for the specified patient case.
- List Patients
Returns Cliniko patients, optionally filtered (e.g. updated after a date) and sorted, with the total count.
- 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).
- Upload patient attachment
Uploads a file, such as a PDF, to a patient's record in Cliniko as an attachment.
- Add annotation
Creates an annotation in Fullstory to mark an event such as a release on your session and metric timelines.
- Add user
Creates a Fullstory user, or updates the existing user with the same User ID.
- Delete user
Deletes a single Fullstory user by their Fullstory-generated user id.
- Find users
Finds Fullstory users matching a uid, email, display name or identified status.
- Get user
Returns the details of a single Fullstory user, including their custom user properties.
- Set User Properties
Updates an existing Fullstory user's custom properties, display name, email or application user id.
- Track Event
Creates a custom server event in Fullstory, optionally attached to an existing session or user.
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 Fullstory
HubSpot to FullstoryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FullstorySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FullstorySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FullstoryGoogle Sheets
Gmail to FullstoryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FullstoryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cliniko and Fullstory, 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 Fullstory when something happens in Cliniko?
Any of Fullstory's 7 actions, including Add annotation, Add user, Find users and Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fullstory to Cliniko?
Fullstory has no triggers in the catalog today, so automations start in Cliniko. If you need the other direction, ask: your agent reads Fullstory's API documentation and adds it.
Do I have to build a connector for Cliniko or Fullstory?
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 Fullstory 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.