Morning file loading
Someone downloads the bank's file, opens it, fixes it and loads it before posting can start.
Payment files, billing exports and accounting systems move on schedules. SentraBridge loads and checks them, emails exceptions to finance, and keeps no copy of the payment data.
Someone downloads the bank's file, opens it, fixes it and loads it before posting can start.
A malformed row stops the load or, worse, loads wrong.
Some movements of money shouldn't happen without a person approving.
CSV, JSON, JSON Lines and XML from SFTP, with host-key pinning and archive after read.
Learn more →Required fields, number and date checks; bad rows go to finance as a CSV attachment.
Learn more →Pause a flow until a person approves. It holds record IDs only and re-reads on approval.
Learn more →Generated from SentraBridge's ready-made templates.
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…
Sentra 311 → SFTP serverEvery night, writes yesterday's changed Sentra 311 requests to a dated CSV file in an SFTP folder for another system to pick up.
A reusable sub-flow: other flows hand it the records that failed their checks, and it emails the data team a summary with a CSV attached.
Each links to its connector page. Not listed? Any REST API, OpenAPI file, database or SFTP server works.
Tyler Munis is listed, but it needs the city's Tyler API access. Many finance teams also exchange files over SFTP, which SentraBridge handles directly.
No. Rows are held in memory while the flow runs. History keeps counts, timings and record IDs.
You choose: leave it, move it to an archive folder, or delete it, after a good run.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.