Skip to main content
An agent is a small automation you draw rather than code: something starts it, it does a few steps, it stops. Use it for jobs nobody wants to do by hand — triaging an inbox, drafting a follow-up, tagging a form.

​
What you’re looking at

The page is headed Agent Builder — “Build AI agents and workflows with custom logic and tools.” The header carries Runs (every execution, with what it did and what it cost), + Create — “Name your agent. You can design it on the canvas next.” — and Public UIs once your plan includes any. Below sits Your agents and a template gallery. The node palette is grouped: Every graph also has a Start node, added for you. Only Agent and Classify consume credits — they carry a billable pill in the inspector. Everything else is free to run: File search is “Deterministic — no model, no credit.” Across the top of the canvas sit the status chips — ”● Live · v3” for what is deployed and “Draft · v4” for what you are editing — plus a Saved indicator and your credit balance. On the Free plan there is no canvas at all: the page shows an upgrade panel for Agent Studio — “Build AI agent virtual assistants on any paid plan.”

​
Build and deploy an agent

1

Create the workflow

Select + Create, name it — “Agent name (e.g. Appointment reminder)” — and select Create. The canvas opens.
2

Choose what starts it

Select the Start node and set its Trigger: Manual / Preview for testing; a Schedule of Every 15 minutes, Every 30 minutes, Every hour, Every day or Every week; Webhook / API call; an inbound message (Inbound SMS, WhatsApp, email, fax or phone call (voice)); or one of around fifty events such as Appointment booked.
3

Lay out the steps

Drag nodes from the palette and connect them. Start with one Agent node and an End; add Classify and If / else once that works. Put a User approval node in front of anything that sends, charges or writes to a record.
4

Test it by hand

Run it manually and read the result under Runs — this is where you find out what your instructions actually said, as opposed to what you meant.
5

Deploy it

Select Deploy. A toast confirms it — “Deployed — v1 is now live” — and the chip changes to Live. Later edits sit in the draft until you Redeploy.
A saved draft does nothing. The builder says so under the trigger: “Event & schedule triggers take effect after you Deploy.” A Webhook / API call trigger needs one more step — the endpoint has to be switched on under Settings → AI settings, and that card is a Team feature. See AI settings.
Agent and Classify steps consume credits every time they run, and a schedule multiplies that: Every 15 minutes is 96 runs a day, roughly 2,900 a month, times the billable nodes in the flow. Start on Every day, watch the cost under Runs, and shorten the interval only once you know what one run costs. See Agent credits.

​
What your plan allows

Drafts are unlimited on every paid plan; publishing is what is capped. The limit is reported when you try to deploy past it: “Your Starter plan can publish up to 5 agents or automations at a time. Drafts are always unlimited. Upgrade to Essential to publish more.” Undeploying one frees the slot, so you can rotate rather than upgrade.

​
Where the depth lives

This page is the map; the detail sits in the platform section:

​
Who can do this

  • Enforcement is opt-in, per person. Someone never saved in the permissions sheet is unrestricted, and the sheet warns “Saving starts enforcing”.
  • A denied action is recorded; an allowed one is not. Hiding AI Agents from a sidebar is a convenience, not a security boundary. A credit figure you may not see renders as a dash, not a zero.
See Staff permissions.

​
Check it worked

  • The chip at the top of the canvas reads Live with a version number, not just Draft.
  • A manual run appears under Runs with its steps and its cost.
  • A scheduled agent produces a run at the next interval without you touching anything.
  • A webhook agent produces a run when the other system calls it — nothing at all means the endpoint is still disabled in AI settings.

​
Common issues

It is still a draft. “Event & schedule triggers take effect after you Deploy” — select Deploy.
Deploying is only half of it. The endpoint has to be enabled under Settings → AI settings, and that card is a Team feature. See AI settings.
You are at your plan’s deployed limit: “Your Starter plan can publish up to 5 agents or automations at a time. Drafts are always unlimited. Upgrade to Essential to publish more.” Undeploy one, or move up a plan.
Check the schedule interval and the number of Agent and Classify nodes — every one bills on every run. Runs shows the cost per execution.
Put a User approval node in front of the sending step and redeploy. See AI safety.
Your plan includes none — “Public Agent UIs are available on the Starter plan and above.” See Publishing agents.

​
FAQ

No. Drafts are unlimited on every paid plan, and credits are consumed only when an Agent or Classify step actually executes.
Only through the tools you give it, and within the safeguards in AI safety. It has no standing access to anything you have not wired to it.
Your edits sit in the draft — the chips show Live · v3 and Draft · v4 side by side. The version running is the one you last deployed.
Yes. Undeploy it — the design is kept and the slot is freed.
Classify sorts an input into one of your categories and pairs with If / else to branch. Agent reasons and writes. Both bill, but Classify is the cheaper way to route.