Database → transform → database (upsert)
Reads customers out of the demo database, reshapes them with a mapping, and upserts them into demo.orders keyed on order_ref. Running it twice is the point: the row count does not move, because an upsert matched every row it had already written.
The pipeline
This is the actual graph the template creates — 3 steps.
Connects to
- PostgreSQL
How you know it worked
demo.orders started empty. After one run it holds five rows, one per customer. Run it a second time and it still holds five — that is the upsert matching on order_ref rather than inserting duplicates. (updated_at does not move: the write sets only the three columns the mapping names, which is what a column-mapped write means.)
Try this templateUsed in: Education & government
Related templates
Directory group → email report
Looks a group up in the directory and emails its membership as an attachment. Reads the group entry's own member list, so it works against a plain…
A published app with a multi-page front end on a file databaseSchool management system (app + front end)
A whole small app on a local SQLite file: students, classes and attendance, with a multi-page front end you open in the browser. The 'setup'…
Rendered documentsStudent mark sheet (PDF)
Rows from a database become one designed document: a student's marks, one row per subject, rendered into a printable statement of marks with a…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.