Describe am
One sentence enter, workflow come out
The hardest part of building automation no be the building itself. Na the blank canvas, the four hundred integrations inside search box, and the quiet suspicion say you go spend one afternoon on something wey suppose take ten minutes. Dem don remove that part here.
Wetin you type
Plain words, for your own language, about the work wey you want make dem do. No template to pick. No keywords to guess. The sentences wey people really dey write be like this:
“When order don pay, raise the invoice, drop the stock count, and text the customer tracking link the moment e ship.”
“Every Monday at seven, pull last week bookings, work out which venues no reach half full, and e-mail me list wey dem sort worst first.”
“If severe weather warning appear anywhere wey our crews dey work, text the crew leads — even for night — and open note for the duty manager.”
Longer better pass shorter, and specific better pass tidy. If the wait suppose be two days no be one, talk am. If message must go out in Polish, talk am. Anything wey you no talk go become default wey you go change later, e no be disaster — na just one minute wey you no suppose spend.
Wetin happen for the two minutes
Dem go read your sentence into intent: wetin start am, wetin must happen, for which order, and wetin must be true at each point. Dem go then resolve that intent against the catalogue of steps wey really exist — your connected accounts, the castomAPI services for your plan, and plain HTTP for everything else.
Then dem go assemble the workflow. Steps in order. Branches where decision really need. Waits where the sentence show say patience dey need. Field mappings wey dem guess from the shapes involved, and dem mark am as guess where the guess no strong.
Finally dem go check am: every step required input get source, every branch get both paths defined, and every connection either dey exist or dem flag am as one wey you still need make. The workflow wey go land in front of you na workflow wey fit run, no be diagram of one.
Wetin you go get back
Editable workflow, wey dem switch off, with to-do list attach: the connections wey e need, the guesses wey e make, and the values wey e no fit infer. Work down the list and e ready.
- ⚡Trigger wey dem chooseWebhook ·
order.paid. Signature verification dey on by default. - 2StepCheck the delivery address against reference data.
- 3StepRaise di invoice. Di fields don map from di order.
- 4StepReduce stock. Di idempotency key na di order id.
- 5WaitUntil di shipping webhook land, or 5 days pass, whichever come first.
- 6StepSMS wey get short link, and we dey count di redirects.
- !E need youTwo connections to authorise. One field wey we guess wey you go confirm: VAT rate.
E off until you talk am say make e onNothing don run yet
Two minutes from now, dis one go be process wey dey work.
Den you go take am over
Set am up exactly di way you want am
Dis na di part wey matter, and na di part wey di two minutes buy you time for.
Change anything
Add step, delete one, arrange dem again, split branch, replace AI step with deterministic one because you see say di rule simple after all.
Talk am with your own words
Every message wey di workflow send na text wey you fit edit. Di draft na starting point and e read like one; di version wey go out suppose sound like you.
Simulate am
Push one real record through and read back di exact path, every value, every message wey e for send. Nothing comot from di building during simulation.
To build am yourself still be di normal thing to do
Plenty people no ever type one sentence. Dem go open empty workflow, drop trigger inside, add steps and continue — and for three-step job, dat one dey often faster than to describe am. Description dey worth am for di twelve-step job wey get four branches and one wait, na dat one you don dey postpone.
You fit still describe change to workflow wey already dey: “make una still send warehouse note when di order pass one thousand zloty” go come as proposed edit, dem go show am as diff against wetin you get, and you go accept or reject am. Nothing dey apply to live workflow if you no talk am.
About di two minutes: na description of di usual case, no be guarantee. Short workflow dey faster; long one with connections wey you no sabi dey take more time. Wetin dey fixed na di shape of di deal — you write prose, you get working thing back, and you spend your attention on di parts wey only you fit decide.