Skip to main content
Agents are built in Agent Studio; this tab holds the account-level things they depend on — the credit balance, the outside tools they may call, and the endpoint that lets another system start them.

​
What this tab controls

The page is headed AI settings — “Agent Studio credits, connected tools (MCP), and agent-to-agent access.”

​
Connected tools

​
Webhook / API trigger

Every agent step consumes credits from the hospital’s balance. A webhook wired into a busy system can fire agents far more often than anyone expects, so turn it on knowing what will call it and how often — and disable it while you are testing the sending side. Credits are covered in Agent credits.

​
Set it up

1

Check the credit balance

The Agent credits card shows what is left. An agent with no credits will not run.
2

Connect an external tool

Select Add MCP server, name it, paste its URL, and pick the auth it needs. Use Test first — it reports the tool count and names, so a wrong URL is caught before you save.
3

Authorise it

For OAuth, choose Add & Connect and sign in through the window that opens. It confirms with “MCP server connected”.
4

Open the Webhook / API trigger card

Expand it. It explains itself: “Give this endpoint to Zapier, a form backend, another app, or any script.”
5

Copy the endpoint and the secret

Copy the Endpoint URL, then Reveal and copy the Signing secret into the sending system as SIGNING_SECRET. Use Copy snippet for the exact signing recipe.
6

Enable it

Switch the endpoint to Enabled. It confirms with “Webhook endpoint enabled”.

​
What changes once you save

Connecting a tool makes it selectable as a step in Agent Studio. Nothing calls it until an agent is built to. When it is called, identifying details are stripped before anything reaches a third party — the tool sees the shape of the request, not the patient behind it. Removing a server takes it away from every agent immediately; an agent that depended on it fails that step rather than silently skipping it. Enabling the webhook opens a single endpoint. A correctly signed POST fires every published agent whose start trigger is “Webhook / API call” — or a custom event matching the request’s event field — and the JSON body becomes that run’s input. The important consequence runs the other way: a webhook-triggered agent will not fire at all until the trigger is enabled here. An agent can be published, correct and waiting, and nothing happens because this switch is off. Check it first when a trigger appears dead. Rotating the secret takes effect instantly. “The current secret stops working immediately. Any external system signing requests with the old secret will start getting 401 errors until you update it with the new secret.” Rotate when someone leaves, or when the secret has been pasted somewhere it should not have been — then update every sender. Requests older than five minutes are rejected, and a repeat carrying the same idempotency key is treated as a duplicate rather than run twice. Agent behaviour itself is set per agent in Agents, not here.

​
Check it worked

A connected tool shows in the list with its URL and, for OAuth, a green OAuth badge. For the webhook, send one signed test request from the outside system: the agent should appear in its run history with your JSON as its input, and the credit balance should drop by what that run cost.

​
Common issues

“Let any external system (Zapier, a form backend, another app) fire your agents by POSTing a signed request to your clinic’s webhook endpoint. Available on the Team plan.”
Accountants can reach settings but not the trigger card.
Either the signature does not match, or the secret was rotated and the sender still holds the old one. Re-copy the secret and re-check the signing snippet.
No published agent has “Webhook / API call” as its start trigger, or its custom event does not match the event in your request body.
The URL is wrong or the server needs auth you have not supplied. Switch to Bearer token or OAuth and test again.
Its authorisation expired. Select the refresh icon on the row and sign in again.