Loops
Compose CRM workflows as node graphs that trigger, gather, decide, and route through your approval inbox.
A Loop is a directed graph: a trigger kicks off, a chain of data, agent, and human checkpoint nodes shape the work, and action or approval nodes route through real CRM service paths. Every approval still flows through your inbox: you approve, the lead status changes, the email sends, the task lands.
The killer demo
A Marbella agent says "I have ten buyers for penthouses above one million." Autopilot scaffolds a Loop:
trigger.cron (02:00)
→ data.propertySearch.resales (price > 1M, beds ≥ 3, Marbella)
→ human.review ("pick three for brochures")
→ agent.brochureGenerator
→ data.leadMatch
→ agent.personalizedEmail
→ human.approve ("review and send")
The user wakes up at 09:00 to a quiet "3 awaiting your review" pulse, ticks three properties, lands at the approval inbox at 09:05 with pre-drafted personalised emails ready to one-click send.
Where to go next
- Node catalog: every node kind, its input and output types, and what it connects to.
- Runs: how a run progresses, how to resume at a paused human checkpoint, how to cancel.
- Triggers: manual, schedule, and event triggers.
- Scaffolding with Autopilot: how to ask Autopilot to design a Loop from a one-line description.
Related Articles
Node catalog
Every kind of node in a Loop: triggers, data sources, agents, human checkpoints, actions, and displays.
Runs and resume
How a Loop run progresses on the canvas, how nodes light up live, how to resume a checkpoint or retry a failure, and how to inspect past runs.
Triggers
Manual, schedule, and event triggers — how runs get started.