Integration

Connect Beanstalk and Cliniko

When New User fires in Beanstalk, your agent runs Find patient by email in Cliniko, or New or updated contact in Cliniko to Get User in Beanstalk. 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 Beanstalk and Cliniko 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)

Beanstalk holds the repositories and user accounts for the software your practice runs on, while Cliniko holds the people side — patients, contacts and practitioners. Joining them means a developer added in Beanstalk shows up as a contact in Cliniko, and a new practitioner in Cliniko can have a repository waiting for them.

Example flows

What Beanstalk and Cliniko can do together

From Beanstalk to Cliniko

From Cliniko to Beanstalk

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 Beanstalk and Cliniko

Triggers and actions 19 triggers · 43 actions

Each app on its own

Reviews

What our customers say

More from Beanstalk

More into Cliniko

Questions

Beanstalk and Cliniko, answered

Can a new Beanstalk user become a record in Cliniko automatically?

Yes. The New User trigger in Beanstalk starts the run, Get User pulls the full details, and Cliniko can create a contact or look one up by email address. If a matching contact is found, Update contact writes the Beanstalk details onto it.

Can Cliniko activity create things in Beanstalk?

It can. A new or updated practitioner in Cliniko can trigger Create Repository in Beanstalk, and a new or updated contact carrying an SSH key can trigger Add public key. Both rest on listed triggers and actions, and the agent tests each scenario before it runs.

What can start an automation from Beanstalk?

Any of Beanstalk's 2 triggers in the catalog, including New User and New Repository. Describe the moment in plain language and your agent picks the right one.

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

Any of Cliniko's 36 actions, including Find patient by email, Create contact, Create patient and Update contact. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Cliniko to Beanstalk?

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

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

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 Beanstalk and Cliniko 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.