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.
Automation
Turn reliable signals into useful work, with a clear test, decision, evidence and recovery path for every run.
Approval inbox
Decide from the frozen version and trigger facts.
No sample runs are waiting for a decision.
Operational readiness
Explore the current Automation layout with fictional records. Search, switch views and try both themes. 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 internal-work recipes with supported triggers, conditions, delays and approvals. Keep a versioned record of exactly what was published; connected products govern their own supported actions.
- 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.
More of the working product
What you can do with Automation.
Explore the tools behind the overview, then open a workflow for the steps, settings and availability that apply. Product access, rollout and connected providers determine what your workspace can use.
Recipe lifecycle
- Start with a named recipe draft.
- Test it before publication.
- Publish a fixed version and create a new version for changes.
Trigger/limits
- Trigger work manually, on a schedule or through an authenticated connector.
- Add a supported text condition or delay.
- Set run limits, a stop date or a maximum run count.
Internal work
- Define the task’s title, summary and priority.
- Choose the supported task destination for the recipe.
- Keep the task linked to its source and responsible person.
Event prep lists
- Prepare a list of one to thirty tasks.
- Assign a person, eligible Event team members or a rota role.
- Use current published cover and keep missing cover visible.
Approval
- Review the exact saved proposal before approval.
- Give a reason when rejecting it.
- Check current permission for the original work separately.
Operations
- Inspect run results and grouped causes of exceptions.
- Use replay or compensation only where supported.
- Pause, resume or retire recipes and rotate connector keys.
The general recipe builder creates internal work. Event task lists are prepared functionality subject to rollout; connected products retain their own actions and approvals.
Explore every workflow in the guides.
Choose a guide to see all its topics. The detailed guides include setup requirements, preview features and supported limits.
Automation3 workflow topics
Configure available recipes and follow approvals, outcomes and recovery.
Read the complete guideTasks, checklists and My Work4 workflow topics
Track tasks and checklists and find personal follow-ups in My Work.
Read the complete guidePart 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