Three 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 takes a count of the orders table before anything touches it, loads the orders, then emails the summary — and the summary is allowed to fail without failing the intake.
Connects to
- PostgreSQL
Also includes
- Sequence
How you know it worked
Open Sequences on the project, pick demo-order-intake and press Run. The run log shows three rows, in order, each with the pipeline it ran and its own status — that is the whole difference between a sequence and a pipeline that happens to do three things.
Try this templateUsed in: Retail & e-commerce
Related templates
Webhook → 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 —…
Published appOne app, one URL namespace (published app)
A published app groups things you have already published under a single URL — /apps/demo-shop/v1/… — with its own OpenAPI document. This one binds…
Per-location totals joined to settlement, variances emailedRestaurant nightly close (POS vs card settlement)
What every area manager does by hand after service: take the POS sales for each location, take what the card processor actually settled, and find…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.