Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
ExampleTemplate

Load the bank's daily payment file into the city database

Every morning, reads new payment CSV files from the bank's SFTP folder, cleans and checks them, loads them into a database table, and archives the files. Bad rows are emailed to finance.

Try it on your dataAll examples
This flow

5 steps

StartsOn a schedule
SystemsSFTP server, PostgreSQL / PostGIS
Branches1
Stored recordsNone: pass-through
§ The flow

The whole flow, as it appears on the canvas.

Scroll sideways on small screens. Colors show the kind of step: start, read, change, decide, write.

Flow diagram: Load the bank's daily payment file into the city databaseEvery morning, reads new payment CSV files from the bank's SFTP folder, cleans and checks them, loads them into a database table, and archives the files. Bad rows are emailed to finance.Weekdays at 6 amOn a scheduleRead payment filesRead files · SFTPClean and checkApply rulesLoad intoutility_paymentsWrite to database · PostgreSQLEmail bad rows tofinanceSend emailInvalid
StartReadFilesDatabaseChangeDecideWriteAct
§ Step by step

What each step does.

  1. 01 · Start · On a schedule

    Weekdays at 6 am

    • Weekdays at 6:00 am (workspace time zone)

    Then: Read payment files

  2. 02 · Files · Read files · SFTP server

    Read payment files

    • Reads files matching utility-payments-*.csv in inbox on SFTP server
    • Format: CSV, first row has the field names
    • Only files new since the last good run
    • After a good run, files move to archive

    Then: Clean and check

  3. 03 · Change · Apply rules

    Clean and check

    • account: trim
    • account: upper
    • account: required (else “Missing account number”)
    • amount: number
    • amount: between 0.01,100000 (else “Amount out of range”)
    • receipt: required (else “Missing receipt number”)
    • method: lower
    • Records that fail a check leave by the Invalid output

    Then: Load into utility_payments; Invalid → Email bad rows to finance

  4. 04 · Database · Write to database · PostgreSQL / PostGIS

    Load into utility_payments

    • Upserts rows in utility_payments keyed on receipt
  5. 05 · Act · Send email

    Email bad rows to finance

    • Emails [email protected]: “{{count}} payment rows need a look”
    • One summary email
    • Records attached as CSV
§ Systems

Connectors used

Swap any of them for another system with the same kind of data.

§ Next

Keep exploring

SolutionPayment & finance filesSolutionUtility billingExampleCopy 311 requests into the city database, with map pointsExample311 triage: route every request to the right system

Run this flow on your systems.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.

Request a demoBrowse live examples