Your database is a system too.
Read it, write it, watch it.
SQL Server, PostgreSQL/PostGIS and MySQL/MariaDB work as sources and destinations. Read a table or a read-only query, upsert rows, look up values, and push changes back to your APIs.
A table, or a read-only query.
Pick a table and the columns you need, add conditions, and read only the rows changed since the last good run using a change-time column. Or write a single SELECT: it runs in a read-only transaction, and table and column names are checked against the database before use.
- Row ID column for replay and lineage
- Most rows per run, so a first run can't flood a destination
- TLS to the database, on by default for SQL Server
| id | title | updated_at | |
|---|---|---|---|
| 1042 | Pothole on Elm St | 2026-11-09 08:14 | |
| 1043 | Streetlight out | 2026-11-09 09:02 | |
| 1044 | Graffiti, 5th Ave | 2026-11-10 06:41 | changed |
| 1039 | Sidewalk trip hazard | 2026-11-10 07:03 | changed |
Insert, update or upsert.
Write to database adds rows, updates existing ones, or does whichever fits (upsert) using the key columns you choose. It can build a map point column from latitude and longitude in any spatial reference. A bad row is logged and the rest keep going, or the run stops: your choice.
- Key columns that identify a row
- PostGIS geometry from lat/lng (SRID 4326 by default)
- Look up in database: enrich records from any table
From the warehouse back to the apps.
Data doesn't only flow into the database. Read changed rows and create or update records in Sentra 311, Accela or any API, so phone-in work orders and inspection results show up where staff work.
- Database change triggers start a flow when rows change
- Polling with a watermark, SQL Server Change Tracking or PostgreSQL LISTEN/NOTIFY
- Same rules, maps and inspector as any other flow
See it in real flows.
Copy 311 requests into the city database, with map points
Every 15 minutes, upserts new and changed Sentra 311 requests into a PostGIS table, with a map point built from latitude and longitude.
PostgreSQL / PostGIS → Sentra 311Reverse sync: database work orders become Sentra 311 requests
Every 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work…
PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP serverPermit pipeline: map issued, report finaled, file expired
Nightly, reads changed permits with a SQL query, cleans and checks them, then puts issued permits on the ArcGIS map, emails building a total of…
Questions, answered
Can a query change data?
No. Custom queries must be a single SELECT and run in a read-only transaction. Writes go through the Write to database step, where you choose the table, action and key columns.
Does SentraBridge copy our tables?
No. Rows are read into memory for the run and dropped. There are no staging tables.
Which databases?
Microsoft SQL Server, PostgreSQL (with PostGIS) and MySQL/MariaDB.
See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.