Describe it
One sentence in,a workflow out.
The hardest part of building an automation has never been the building. It is the blank canvas, the four hundred integrations in a search box, and the quiet suspicion that you are about to spend an afternoon on something that ought to take ten minutes. That part is removed here.
What you type.
Plain words, in your own language, about the job you want done. No template to pick. No keywords to guess. The sentences people actually write look like this:
“When an order is paid, raise the invoice, drop the stock count, and text the customer a tracking link the moment it ships.”
“Every Monday at seven, pull last week's bookings, work out which venues are under half full, and e-mail me a list sorted worst first.”
“If a severe weather warning appears anywhere we have crews working, text the crew leads — even at night — and open a note for the duty manager.”
Longer is better than shorter, and specific is better than tidy. If a wait should be two days rather than one, say so. If a message must go out in Polish, say so. Anything you leave out becomes a default you will change later, which is not a disaster — just a minute you did not have to spend.
What happens in the two minutes.
Your sentence is read into an intent: what starts this, what has to happen, in what order, and what has to be true at each point. That intent is then resolved against the catalogue of steps that actually exist — your connected accounts, the castomAPI services on your plan, and plain HTTP for everything else.
Then the workflow is assembled. Steps in order. Branches where a decision is genuinely needed. Waits where the sentence implies patience. Field mappings guessed from the shapes involved, and marked as guesses where the guess was not confident.
Finally it is checked: every step's required input has a source, every branch has both paths defined, and every connection either exists or is flagged as one you still have to make. The workflow that lands in front of you is a workflow that could run, not a diagram of one.
What you get back.
An editable workflow, switched off, with a to-do list attached: the connections it needs, the guesses it made, and the values it could not infer. Work down the list and it is ready.
- ⚡Trigger chosenWebhook ·
order.paid. Signature verification switched on by default. - 2StepValidate the delivery address against reference data.
- 3StepRaise the invoice. Fields mapped from the order.
- 4StepDecrement stock. Idempotency key set to the order id.
- 5WaitUntil the shipping webhook arrives, or 5 days, whichever comes first.
- 6StepSMS with a short link, redirects counted.
- !Needs youTwo connections to authorise. One guessed field to confirm: VAT rate.
Switched off until you say otherwiseNothing has run
Two minutes from now,
this is a working process.
Then you take it over
Set it up your way.
This is the part that matters, and it is the part the two minutes bought you time for.
Change anything
Add a step, delete one, reorder them, split a branch, replace an AI step with a deterministic one because you realised the rule is simple after all.
Say it in your own words
Every message the workflow sends is text you can edit. The draft is a starting point and it reads like one; the version that goes out should sound like you.
Simulate it
Push a real record through and read back the exact path, every value, every message it would have sent. Nothing leaves the building during a simulation.
Prefer to build it yourself?
That is still normal.
Plenty of people never type a sentence. They open an empty workflow, drop in a trigger, add steps and get on with it — and for a three-step job that is often faster than describing it. Description earns its keep on the twelve-step job with four branches and a wait, which is the one you have been putting off.
You can also describe a change to a workflow that already exists: “also send the warehouse a note when the order is over a thousand zloty” arrives as a proposed edit, shown as a diff against what you have, and you accept or reject it. Nothing is applied to a live workflow without you saying so.
On the two minutes: it is a description of the usual case, not a guarantee. A short workflow is quicker; a long one with unfamiliar connections takes longer. What is fixed is the shape of the deal — you write prose, you get a working thing back, and you spend your attention on the parts only you can decide.