Let evidence write the first draft.
When this happens, the right work follows.
Turn trusted operational evidence into governed, reviewed action without hiding the decision trail.
In the product today
Manual and scheduled workflows, supported connector triggers, versioned recipes, dry-runs, publishing, pausing, approvals, retries and run history.
See what’s nextThe Automation overview, showing responsibility, connected work areas and operational readiness.
Current workspace layouts with sample data. Nothing is saved or sent.
11 · Work area
Automation
Turn reliable signals into useful work, with a clear test, decision, evidence and recovery path for every run.
Operational readiness
Based on the current Automation workspace. Search and switch views using sample records. Nothing is saved, sent or charged.
On the other side of the shift
Less friction. More getting on with it.
- 01
Preserve source evidence before normalising it.
- 02
Put approvals and exceptions inside the operating flow.
- 03
Carry approved actions through attributable execution.
What’s included
Made for the job.
The practical details behind the promise. Built around the people doing the work, and connected to the information they need.
- 01
Versioned recipes
Build a workflow with triggers, conditions, delays, actions and approvals. Keep a versioned record of exactly what was published.
- 02
Manual, scheduled and connected triggers
Start work yourself, run it on a schedule or respond to supported events from another enabled product.
- 03
Test before publish
Draft, dry-run, test, publish, pause and retire a recipe without turning an experiment into a live external effect.
- 04
Approvals and exceptions
Hold high-risk steps for review and keep skipped, failed or blocked work visible to the responsible operator.
- 05
Runs, retries and replay
See what triggered a run, what each step did, where it stopped and how it was retried or recovered.
Part of the bigger picture
The context comes with it.
The guest, the venue, the team. Useful information should follow the work. Automation connects to shared records, with access controlled for your organisation and your people.
A clear picture
Today. And what’s next.
Manual and scheduled workflows, supported connector triggers, versioned recipes, dry-runs, publishing, pausing, approvals, retries and run history.
Automation supports the actions each enabled product exposes. It is not a universal agent that can take any action or bypass that product’s permissions and approvals.
Good questions
Automation FAQs.
How does Automation work with other Soupy products?
Other products publish trusted facts and expose governed actions while Automation remains independently entitled and cannot bypass their authority.
Does Soupy overwrite source EPOS data?
No. Source evidence is retained append-only while mappings, normalised facts and later corrections remain attributable.
Can automation bypass approval?
External effects remain governed by the recipe, capability and approval boundary attached to the action.
Does the product preview place a stock order?
No. It demonstrates a reviewed draft and clearly states that nothing is moved or ordered.
Start with the pressure point