Branch on anything
Route by value, customer, country or whatever the last step returned.
The process you already run,
Lay out the steps once. From then on it runs the same way every time, at any hour, on every order, ticket and invoice that comes in. You keep the decisions that matter.
Order intake · run #2,104● Running
4 steps done1.8s elapsed0 errorsEvery step written to the log
Same result
On the thousandth run as the first
No code
Built and changed in the editor
Every run
Logged step by step, exportable
Your call
Approval gates wherever you want them
Work arrives, the workflow starts
Nothing to remember and nobody to chase. The systems you already use kick it off.
REST API
Any system you run
Email
Inbound messages
Stripe
Payments and disputes
Shopify
Orders and customers
Jira
Issue events
Telegram
Bot messages
Web chat
Widget on your site
Schedule
Hourly, daily, monthly
Anything with an API can start a run. If it can send an HTTP request, it is already supported.
Drag the steps, not the deadline
The editor is a canvas: drop in a step, connect it, configure it on the right. The people who know the process can read it, which is usually the difference between an automation that survives and one that does not.
- Steps you can name in plain language
- Run the draft while the deployed version keeps serving
- Change it without waiting on a release
- Every deployed version kept and readable
Steps
AI step
Condition
API call
Data store
Approval
Email
AI step
Model
Balanced
Tools
3 enabled
Output
JSON
On error
Retry ×2
Real processes are not straight lines
Branches, retries, waiting on a person. The awkward parts are where most automations give up.
Loop over lists
Handle a hundred line items the same way you handle one.
Wait for a person
Pause mid-run for a review, then carry on exactly where it stopped.
Retry and recover
Rate limits and 5xx from Jira, search and webhooks are retried rather than dropped.
Guardrails
Check the output against your rules before anything leaves the building.
Run the draft
Try a change on the draft version while the deployed one keeps serving traffic.
When someone asks what happened, you can show them
Each run writes a timestamped record: what came in, what each step decided, which model ran, what it cost, what went out. It is the difference between trusting an automation and hoping.
- Inputs and outputs on every step
- The model used and the tokens spent
- Failures with the actual error, not a shrug
- Exportable for audit and compliance
Execution logrun #7,731 · exportable
09:14:02.118TriggerOrder #7731 received
09:14:02.140Check stockGET /inventory/7731 → 200
09:14:02.362Conditionin_stock = false → Backorder
09:14:02.377Data store3 matching supplier records
09:14:03.901AI stepDrafted customer note · 412 tokens
09:14:03.944ApprovalWaiting on Elena (credit over 500 EUR)
Nothing hidden: inputs, outputs, model used and cost, on every step.
Pick the process nobody wants to own
The best first workflow is boring, frequent and annoying. Those pay for themselves fastest.
Invoice and expense intake
Read the document, match it to a PO, flag the exceptions, push the rest through.
Ticket triage and routing
Classify what came in, set priority, attach the history, land it with the right team.
Lead enrichment and routing
Fill in what the form did not ask, score it, assign it, notify the owner.
Order and returns handling
Stock checks, backorder notices, refund eligibility, courier updates.
Scheduled reporting
Pull the numbers on a schedule, write the summary, send it before the meeting.
Customer and staff onboarding
Kick off the accounts, the documents and the reminders from one trigger.
Invoice intakeTicket triageLead routingStock checksRefund eligibilityScheduled reportsDocument extractionOnboarding kickoffPayment retriesCourier updatesInvoice intakeTicket triageLead routingStock checksRefund eligibilityScheduled reportsDocument extractionOnboarding kickoffPayment retriesCourier updates
Workflow or agent?
Most companies end up running both. The question is only which one fits the job in front of you.
Use a workflow when
- You can draw the steps on a whiteboard
- The same input should always give the same path
- Auditors will ask why it did that
- Volume is high and the work is repetitive
Use an agent when
- The number of steps is not predictable
- It has to read the situation first
- The work is research, judgment or a conversation
- You would rather set a goal than a script
Bring us your least favourite process
Describe it in a call and we will come back with the workflow mapped out, so you can see the shape of it before committing to anything.