/ product · automations
six triggers. thirteen steps. Zero babysitting.
An automation is one trigger plus ordered steps, run asynchronously on a worker. Branches fork, loops nest, models get invoked — and every run leaves a visible trail.
/ the builder + the trail
Logic you can read top to bottom.
The chain on the left is the automation; the trail on the right is a real run executing it — step by step, in the open.
Automation
record-updated
when a record changes
find-records
step 1
branch
step 2
invoke-model
step 3
update-record
step 4
Run trail
runningrecord-updated
CQ-103 · Record demo video → Blocked
find-records
matched 3 records with status Blocked
branch
owner is set → continue
invoke-model
drafted an unblock summary
update-record
CQ-103 flagged · owner notified
every run leaves this trail — step by step, in the open
/ triggers
Six ways in. Events to cron.
/ steps
Thirteen blocks. Compose anything.
/ records
/ flow
/ utilities
/ recipes
Three flows teams wire on day one.
Blocked-work alerts
The moment something big gets stuck, the right channel knows — no standup required.
Weekly AI digest
Every Monday, a model reads the week ahead and writes the summary into your workspace.
CI status intake
Your pipeline posts a webhook; the launch table reflects reality without anyone pasting.