Onboarding checks as one decision call
The tabs an onboarding officer opens by hand — the identity service on one, the credit bureau and its watchlist flag on another — as one published endpoint that answers in a single round trip. The two branches are fetched at the same time and joined on the applicant, then a condition turns the combined facts into approve, refer or decline. Which branch said what stays on the run trace, so the decision is reconstructable months later.
The pipeline
This is the actual graph the template creates — 11 steps; dashed lines are the failure/invalid paths.
Connects to
- PostgreSQL
How you know it worked
Call it once per applicant and watch the three outcomes fall out of the same graph:
Try this templateUsed in: Banking & finance, Insurance & brokerage
Related templates
Database → CSV on SFTP
Writes a CSV onto the SFTP server — including one deliberately broken row. It exists to give the validate-and-route demo something to find, which…
File in, validation, two destinationsSFTP CSV → validate → database, rejects emailed
Reads the CSV back off SFTP and takes it a row at a time: good rows are loaded into a table, a bad one is emailed to somebody instead of being…
Excel exportDatabase → Excel workbook in object storage
The same rows again, this time as a real .xlsx workbook dropped into MinIO. Nothing about the pipeline changes except the format — that is the…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.