Skip to main content
An agent is a small workflow you draw on a canvas: something starts it, one or more steps do the work, and it ends. Building one is free and unlimited on every plan. Nothing an agent does takes effect until you deploy it.

​
Create the agent

1

Select + Create

The Agent Builder page opens with an Agent credits card, your existing agents, and a gallery of one-select templates. If a template already does roughly what you want, choose it — it lands on the canvas fully wired and you edit from there.
2

Name it

The Create a workflow dialog says “Name your agent. You can design it on the canvas next.” Give it a name that says what it does — the placeholder suggests “Agent name (e.g. Appointment reminder)”. A Description (optional) helps whoever inherits it.
3

Select Create

You land on the canvas. The top bar shows a Draft · v1 badge, your credit balance, and a save indicator that reads Saved once your work is stored. Drafts save themselves as you work.

​
Build it on the canvas

The palette on the left is grouped into four sets. A Start node is always present; you drag in the rest. Select a node to configure it in the panel on the right. See Agent tools and knowledge for what each tool node needs.
Agent and Classify are the two steps that spend agent credits. Every other node is free. A workflow with several Agent steps on a Every 15 minutes schedule will spend credits around the clock once deployed — count the billable steps before you deploy a schedule.

​
Choose what starts it

Select the Start node and pick a trigger.
There is no “when an invoice becomes overdue” trigger, because that is not an event — it is the passage of time. For anything time-based (overdue invoices, following up submitted claims, expiring memberships) use a Schedule trigger with a worklist tool, and let the agent find the records that now qualify.

​
Preview it

Select Preview in the top bar and talk to the agent in a sandbox before anyone else can. Use Playbooks to hand it reusable instructions and Evals to check it still answers correctly after you change something. Preview runs are real runs and spend credits.

​
Deploy it

This is the step everyone misses. A saved draft with a schedule trigger does absolutely nothing — the canvas only becomes live when you deploy it.
1

Select Deploy

The button sits at the top right and reads Deploy the first time, Redeploy afterwards.
2

Confirm it went live

You get “Deployed — v1 is now live” and a green ● Live · v1 badge appears next to the agent’s name. A fresh Draft version opens so you can keep editing without disturbing the live one.
3

Redeploy after every change

Editing a deployed agent edits the draft, not the live version. Your change reaches the running agent only when you select Redeploy.
If your agent uses the Webhook / API call trigger, one more thing has to be switched on before anything can reach it. Open , expand Webhook / API trigger (“let any external system fire your agents”) and turn it on — you get Webhook endpoint enabled. Copy the endpoint and its signing secret from there. You can rotate the secret or disable the endpoint at any time.

​
Check it worked

  • The agent shows a green ● Live badge on the canvas and a published badge on the Agent Builder page.
  • The Runs page lists a run after the trigger has fired once. A manual agent will not appear there until you run it.
  • Your credit balance drops after a run that contains an Agent or Classify step.

​
If something goes wrong

It is almost certainly still a draft. Open it and check for the green ● Live badge — if you only see Draft, select Deploy. Editing a live agent also needs a Redeploy before the change takes effect.
The endpoint is off by default. Turn on Webhook / API trigger under , then confirm you are sending a signed POST to the endpoint shown there. If you rotated the signing secret, update whatever is calling you.
Your plan caps how many agents can be published at once. Free publishes 1, Starter 5, and Essential and Team are unlimited. Take another agent offline or see Publish an agent.
Open Preview and step through it there. Most empty results come from a step whose output the next step never reads, or an Agent node with no instructions. Evals will tell you whether a change made it better or worse.
You are out of credits. Top up from the Agent credits card — see How agent credits are used.

Agent tools and knowledge

Knowledge bases, guardrails, outside tools and human approval.

Publish an agent

The difference between deploying and putting a chat assistant on the web.

Agent credits

What a run costs and how a schedule multiplies it.

AI safety and patient data

What an agent may touch, and what you must review.