Integration

Connect Cliniko and HelloSign

When Cancelled individual appointment fires in Cliniko, your agent runs Get Signature Request Files in HelloSign, or New Signature Request in HelloSign to Find patient by email in Cliniko. 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 HelloSign to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

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)
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)

Connecting Cliniko and HelloSign means the paperwork around a booking follows the patient record. New patients in Cliniko can be sent an intake or consent form to sign in HelloSign, and signature requests coming back can be matched to the right patient file. Cancelled appointments in Cliniko can pull back forms that are still waiting.

Example flows

What Cliniko and HelloSign can do together

From Cliniko to HelloSign

From HelloSign to 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 HelloSign

Triggers and actions 18 triggers · 44 actions

Each app on its own

Reviews

What our customers say

More from Cliniko

More into HelloSign

Questions

Cliniko and HelloSign, answered

Can a form go out automatically when someone becomes a patient in Cliniko?

Yes. The new or updated patient trigger in Cliniko can start a send signature request in HelloSign using the patient's email, and you can add a condition so it only runs when an email address is on file. The agent tests every scenario before it goes live.

What happens to a form that is still unsigned when the appointment is cancelled?

The cancelled individual appointment trigger in Cliniko can run cancel signature request in HelloSign so the patient stops receiving it. If you would rather chase it instead, the same trigger can run send reminder to the signer.

What can start an automation from Cliniko?

Any of Cliniko's 17 triggers in the catalog, including Cancelled individual appointment, New or updated patient, New or updated patient case and New cancelled attendee. Describe the moment in plain language and your agent picks the right one.

What can your agent do in HelloSign when something happens in Cliniko?

Any of HelloSign's 8 actions, including Cancel Signature Request, List Templates, Send Signature Request and Send Reminder. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from HelloSign to Cliniko?

Yes. When something happens in HelloSign, your agent can act in Cliniko too. This page covers both directions: HelloSign's triggers and Cliniko's actions are listed here as well.

Do I have to build a connector for Cliniko or HelloSign?

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 HelloSign 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.