Supplier invoice against the contract price
A supplier's invoice arrives as a file, the way it actually does. It is written to SFTP, read back, cleansed — quantities and prices arrive from a CSV as strings, so they are parsed to numbers before anybody does arithmetic on them — and then joined to the contracted price list. A line for something that is not on contract at all takes the 'invalid' port and is emailed to the buyer; everything else is filed. This is the check nobody has time to do by hand, which is why food cost drift is usually found a quarter late.
The pipeline
This is the actual graph the template creates — 11 steps; dashed lines are the failure/invalid paths.
Connects to
- SFTP
- PostgreSQL
How you know it worked
Five invoice lines, four of them on contract. The saffron is not, so exactly one email reaches the buyer and four lines are posted.
Try this templateUsed in: Restaurants & food service, Logistics & distribution
Related templates
HTTP API → database table
Calls a public JSON API and loads the response into a table, column by column. The classic 'fetch it nightly and keep a copy' shape.
Email notificationEmail 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…
Messaging channels, identities and campaigns, walkable without an appA whole messaging channel, offline (echo channel + campaign)
The E26 channel end to end with no messaging account and nothing running but this API. An `echochat` connection is a loopback app: outbound…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.