Restaurant 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 out where they disagree. The POS lines are grouped into per-location totals — net sales, covers, average check — then joined to the settlement figures. A location whose settlement never arrived takes the 'invalid' port and is emailed the same night, instead of being discovered a week later when nobody can remember the shift.
The pipeline
This is the actual graph the template creates — 10 steps; dashed lines are the failure/invalid paths.
Connects to
- PostgreSQL
How you know it worked
Seven sales lines across three locations become three location rows. Two settled; Harbour did not, so exactly one variance email arrives alongside the group summary.
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.