One menu change, pushed to every channel
A price change edited once and delivered everywhere it has to land. The menu is validated against the group's own rules first — nothing without a name, a price and allergen text goes out — then each item is pushed to the POS database and published as a JSON menu file in object storage, which is the website's copy. An item that fails the rules is quarantined and emailed rather than being published half-finished to one channel and not the other.
The pipeline
This is the actual graph the template creates — 8 steps; dashed lines are the failure/invalid paths.
Connects to
- PostgreSQL
- Amazon S3
How you know it worked
Five items in, four published. The tiramisu has no allergen text, so it is held back from BOTH channels and emailed — which is the point of validating once before the fan-out rather than once per channel.
Try this templateRelated templates
Email a summary with the data attached
The smallest useful notification: read something, email somebody about it, attach it. The email node is a side channel — the payload passes…
Webhook triggerWebhook → database
A pipeline that starts when something posts to it. The webhook's JSON body is the run's starting payload, so the first node already has the data —…
Sequence of pipelinesThree pipelines run as one unit (sequence)
A sequence is orchestration above the run machinery: it runs pipelines you already have, in order, feeding each one's output to the next. This one…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.