Loops

Beta. Loops is still growing. The node catalog is expanding, and some nodes are limited while we build them out. Everything documented here is real and working today.

Loops is the workflow builder Autopilot scaffolds for you: your agency's own automation canvas. A Loop is a directed graph. A trigger kicks it off, a chain of data, agent, and human checkpoint nodes shapes the work, and action nodes route through the same CRM service paths you would use by hand. The control thesis is simple: agent nodes can only propose. Every proposal flows through your approval inbox, where you approve, edit, or dismiss each row before anything fires. You approve, the lead status changes, the email sends, the task lands.

What a Loop looks like

A Marbella agent wants to catch new penthouse buyers every morning and write to them personally, without anything leaving without a check. Autopilot scaffolds a Loop:

trigger.cron (07:00) → data.leadSearch (new Marbella buyers, not yet emailed) → human.review ("pick the ones to write to") → agent.personalizedEmail → human.approve ("review and send")

The agent wakes up to a quiet "3 awaiting your review" pulse, ticks the three buyers worth a personal note, lands at the approval inbox with pre-drafted personalised emails, and one-click sends each one. Nothing was sent that they did not read first.

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.