Set the trigger. Walk away.
A record changes, a schedule fires, a webhook lands, and the next twenty steps run without you. Every step is recorded, and a run that fails at step four resumes at step four.
Four parts, one canvas. A workflow is a trigger, a graph of blocks, and the values each step hands to the next.
Pick what starts it.
Nine trigger kinds, from a record created or one watched attribute changing value to a cron schedule or a signed webhook.
Lay out the steps.
Drop blocks on the canvas and connect them. Filter, if / else and switch split the run into the paths an account actually takes.
Wire the values through.
Every block publishes typed outputs. The picker offers only the steps that already ran, so a reference cannot point at a branch that never happened.
Runaway cycles, caught.
The editor walks every workflow in the workspace and flags any whose own writes would re-fire its own trigger. You learn that before you enable it.
“The renewal chase used to be a calendar reminder and a spreadsheet. It is four blocks now, and nobody thinks about it.”
Start it from anything. Use a signal your book already produces instead of building a new one.
Record events.
A submission is created, a record is deleted, a single watched attribute flips value. The run receives the record and the change that caused it.
Schedules.
Daily, weekly, monthly, or a cron expression in the timezone you name. The renewal sweep runs at six without anyone opening the app.
Webhooks.
A signed URL your carrier or vendor can post to. Every environment gets its own secret, so a leaked test key cannot sign a production call.
On demand.
Run it by hand while you are building it, or put it behind a command on the record so an underwriter fires it from the account in front of them.
Thirty blocks, ten groups. Enough to build the motion without dropping into a script.
Records
Create, find, update or upsert, including a whole product record validated against the product.
Conditions
Filter, if / else and switch send the run down the path this account actually takes.
Delays
Pause for a fixed interval or hold until a date, then pick the run back up.
AI and agents
Classify a record, summarize it, or hand it to an agent that gathers context before it answers.
External calls
Send an HTTP request and read the status, headers and body in the step after it.
Human steps
Stop for an approval, a choice or a typed answer, then carry on with what the person said.
Then watch it run. Every run leaves a record of what it did, so a question about last Tuesday has an answer.
Every step, recorded.
One row per block, with its inputs, its outputs, its status and its duration. Loop iterations are recorded one by one, so you can see which of the forty went wrong.
Resume at step four.
A failed run rewinds to the step that broke and carries on from there, on the definition it started with. It keeps its id, so the whole history stays in one place.
Or start over on the fix.
Retry as new replays the original trigger against the current release, so a workflow you just corrected runs the corrected way. The new run points back at the one it came from.
Automation with the whole book behind it.
Workflows read and write the same records your underwriters do. Nothing is exported, and nothing is a day old.
Bring the process you run by hand.
The renewal checklist, the stale submission chase, the carrier email nobody remembers to send. We will build one of them on the call.
Usually 30 minutes, with an underwriter on the call.