Skip to main content
An agent is an assistant you build that follows steps you define. This tab holds the account-level settings behind them: how many credits you have, which outside tools they may use, and how an outside system can start one. Building the agents themselves happens in Agent Studio.

​
What this tab controls

A webhook is just a web address an outside system can send a message to. When something happens over there — a form is filled in, a record changes — it posts to your address, and that starts an agent here.

​
Set it up

1

Check your credit balance

The Agent credits card shows what you have. Select Top up if you need a refill pack before a busy run.
2

Connect an outside tool

Select Add MCP server, give it a name and its address, then choose how it authenticates. Select Test first — you should see a tick and the tools it offers. Then select Add, or Add & Connect for OAuth, which opens a sign-in window.
3

Open the webhook panel

Select Webhook / API trigger · let any external system fire your agents.
4

Turn the endpoint on

Switch it from Disabled to Enabled. You will see “Webhook endpoint enabled”.
5

Hand over the details

Copy the Endpoint URL, reveal and copy the Signing secret, and select Copy snippet for the signing instructions. Send all three to whoever is building the integration, over a private channel — the secret is a credential.

​
What changes once you save

An agent that uses the webhook trigger will not run at all until the endpoint is enabled here. That is the usual reason a webhook agent looks broken: the agent is published, the outside system is posting, and nothing happens because the switch is off. Once enabled, a correctly signed post fires every published agent whose start trigger is set to a webhook or API call, and the message body becomes that run’s input. A connected tool becomes selectable inside the agent canvas as soon as it saves — an agent step can then call it. Removing one takes it out of the picker; any agent still referencing it will fail at that step. Identifying details are stripped from tool arguments before anything reaches an outside server, so a connected tool never receives client identities. Rotating the signing secret takes effect immediately — the old secret stops working the moment you confirm, and any system still using it starts being refused until it is updated. Turning the endpoint off does the same thing more bluntly.
Every agent step consumes credits from the balance on this card, and each model costs a different amount per run. An agent left on a webhook trigger runs as often as the outside system posts to it, so a misconfigured integration can drain a month’s credits in an afternoon. Watch the balance for the first day after you enable a trigger.

​
Check it worked

For a connected tool, select Test — a tick and a list of tool names means the connection works. For the webhook, ask whoever built the integration to send one signed test post; a published agent with a webhook trigger should show a new run in Agent Studio, and the credit balance on this tab should drop.

​
Common issues

The webhook trigger is a Team feature: “Let any external system (Zapier, a form backend, another app) fire your agents by POSTing a signed request to your clinic’s webhook endpoint.” See Change your plan.
Ask an owner or manager. Credits and connected tools are visible more widely.
Someone rotated the signing secret, or the endpoint was switched off. Reveal the current secret, update it in the sending system, and confirm the switch reads Enabled. Requests older than five minutes are also refused, so a badly out-of-sync clock on the sending machine will fail every time.
Its authorisation expired. Select the refresh button on that row to sign in again.
The address is wrong or the server is not publicly reachable. Nothing is saved when a test fails, so correct the address and test again.
You have most likely run out of credits. Check the Agent credits balance and select Top up.