The building blocks of an agent
Drop nodes on a canvas and wire them together. Triggers, conditions, AI steps, delays and webhooks snap into an agent that runs without you.
TriggerWhen something happens
ConditionBranch on the data
AI stepRead, score, decide
DelayWait, then continue
WebhookCall out safely
OutputSend or create
Loop guard built in
Automations that never storm
Every agent carries an origin on its events, so a workflow cannot trip itself into an endless chain. Automations fire once and stop, unless you deliberately opt one into reacting to another.
The first agent most teams ship is the simplest one to trust: a CV lands in the inbox, gets parsed, and becomes a candidate, with no one watching the queue.
First agent
Email arrives
CV is parsed
Candidate created