Loading...
Wrrkflows · automation with humans at the gates
A trigger fires. AI steps read, decide and draft. Then the run stops wherever you put a human — before anything leaves the building. One is running below, and it will wait for you.
Message arrivestrigger · whatsapp
message_received
Read sentimentai_analyze
type: sentiment
Branch on resultcondition
positive / negative
Draft the replyai_compose
style: support
Waiting on youhuman_input
type: approval
Send the replyaction
workflow.send_whatsapp
Open a ticketaction
workflow.create_ticket
You build a wrrkflow by hand — drop a step, wire it to the next. Every step has a name you can read: analyze, branch, compose, wait for a human. What you see on the canvas is exactly what runs.
The step palette
action
send, create, update — the doing step
condition
if / else on any field
ai_analyze
sentiment, intent, urgency
ai_compose
drafts content in your tone
ai_extract
pulls typed fields from text
ai_summarize
bullets, TL;DR, action items
ai_route
picks the right lane for the run
human_input
parks the run for a person
delay
seconds to days
wait_for_event
a reply, a read — or a timeout
loop
iterate over an array
parallel
branches at the same time
transform
maps one shape onto another
http
call an external service
end
terminal — the run is done
15 of the runtime's 18 step types · its own names, not ours
A WhatsApp message. A deal changing stage. A call ending. A cron schedule, a webhook, or you pressing run. Fifteen sources feed the same canvas, and the trigger carries its data into the run.
What can start a run
Sample data · voice triggers require telephony configuration
Analyze reads sentiment, intent and urgency. Compose drafts. Extract pulls typed fields. Any risky action can carry a gate — the AI answers allow, block or review, and its confidence and rationale are written to the run.
ai_analyze · reading the message
Sample dataaction gate · before the send
Every verdict is written to the run · you can always see why
A human-input step parks the run and assigns it to a person. Approve routes one way, reject routes the other. Even the timeout is a decision you configure — never a silent default. Where you want a hand on the send, you wire the gate in front of it.
human_input · the gate, configured
wire a gate and nothing sends without you
Each execution logs every step, its duration and its output. Failures keep the error and the step that raised it. Retries are counted. Runs the gate filtered out get their own bucket — never quietly dropped.
Executions · the honest log
Sample dataFailures keep the error and the step · retries are counted, not hidden
Sample data · not a customer claim. Step names, statuses and thresholds are the runtime's real vocabulary.
Build the wrrkflow once. Approve the moments that matter. Read the receipt after every run.