Automations
46 ways to start. Zero ways to forget.
A visual canvas where triggers chain into actions, conditions branch the path and delays hold the timing. Every handoff you still do by hand — signed contract to invoice, booking to welcome email — mapped once, run every time.
01The canvas
Draw the workflow. That is the workflow.
Four node types — one trigger, then actions, conditions and delays, connected on a drag-and-drop canvas. What you see is exactly what runs.
01 / Triggers
Every corner reports in
Documents sent, viewed and signed; payments received, partial or failed; forms submitted; contacts tagged; bookings made, missed or moved; timers like “3 days before due” — and a manual button when a human should decide.
02 / Actions
25 things it can do next
Communication, document operations, contact and record writes, tag moves, booking updates, webhooks — and one automation can start another, up to five levels deep before the engine stops it on purpose.
03 / Conditions
Branch on what's true
Status, type, amount — compared with precise decimal math — tags, contact and booking fields, days elapsed. Each condition routes to a yes path and a no path; unconnected paths simply end the run.
04 / Delays
Patience, built in
Hours, days, or until a specific moment. A waiting run is persisted, not held in memory — deploys and restarts can't lose it, and it picks up exactly where the delay left off.
02Trust the run
Test it before it touches anything.
05 / Dry run
Rehearse on real data
Pick a real document, contact or booking and run the automation with zero side effects — conditions evaluate against live data so the branching is honest, actions return previews of what they would have done, and delays fast-forward instead of waiting.
06 / Run logs
Node by node, in the open
Every run is logged step by step — inputs, outputs, duration and errors per node. A failed run names the exact step and reason; nothing disappears into a black box.
07 / Cycle protection
Loops die here
An automation that tags a contact, which triggers an automation that tags a contact — the engine has seen it coming. Step caps, depth limits, cooldowns and unique jobs mean a mistake wastes a run, not a weekend.
Outbound calls validate hostnames and pin IPs — private networks are unreachable by construction.
Automation emails are scrubbed before sending, and delivered with your subaccount branding.
Every tag, contact and record an action touches is verified against your agency before it's applied.
A failed run logs and stops — side effects like emails and webhooks are never blindly retried.
“We mapped our onboarding once, in an afternoon. It has run four hundred times since.”
Map it once.
Triggers, branches, delays and dry runs — the automation canvas runs your handoffs so nobody has to remember them.
Flat price. No usage charges. Ever.