One 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 two: a pipeline that lists the latest orders, and the sequence from the demo above. The point is that a caller never learns which is which.
Connects to
- PostgreSQL
Also includes
- Published app
How you know it worked
Two calls to one host, and nothing in either URL says which is a pipeline and which is a sequence:
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 —…
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…
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.