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

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.

Flow diagram: Copy 311 requests into the city database, with map pointsEvery 15 minutes, upserts new and changed Sentra 311 requests into a PostGIS table, with a map point built from latitude and longitude.Every 15 minutesOn a scheduleEvery 15 minutes (workspace time zone)Changed 311 requestsGet records · Sentra 311Reads Service requests from Sentra 311Name fields like thecolumnsMap fieldsShapes each record into 11 fields:request_id, number, category, department, st…Upsert intoservice_requestsWrite to database · PostgreSQLUpserts rows in service_requests keyed onrequest_id
Copy 311 requests into the city database, with map points · 4 steps · a real SentraBridge template
§ 01 / Read

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
work_orders · changed since 2026-11-10 06:002 rows to send
idtitleupdated_at
1042Pothole on Elm St2026-11-09 08:14
1043Streetlight out2026-11-09 09:02
1044Graffiti, 5th Ave2026-11-10 06:41changed
1039Sidewalk trip hazard2026-11-10 07:03changed
Watermark column · SQL Server Change Tracking · PostgreSQL LISTEN/NOTIFY
Illustration: only rows changed since the last good run are read.
§ 02 / Write

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
Flow diagram: 311 triage: route every request to the right systemCleans and checks changed 311 requests, sends bad ones to a data-quality sub-flow, checks the city database to see if each is new, then routes new potholes, lights and trees to Scheduler crews, code cases to the ArcGIS map, and the rest to an SFTP file. Changed requests are upserted into the database with map points, and a summary by department is emailed.Every 15 minutesOn a scheduleChanged 311 requestsGet records · Sentra 311Clean and checkApply rulesData quality alertRun another flowCount by departmentSummarizeAlready in the database?Look up in database · PostgreSQLEmail operationsSend emailNew request?If / elseCrew work?If / elseName like the columnsMap fieldsShape as a crew visitMap fieldsCode enforcement?If / elseUpdate the database copyWrite to database · PostgreSQLCreate Scheduler visitSend records · Sentra SchedulerMap attributesMap fieldsEverything else to SFTPWrite file · SFTPMake map pointMake map pointAdd to the code-casemapSend records · ArcGISInvalidYesYesNoYesNoNo
311 triage: route every request to the right system · 18 steps · a real SentraBridge template
§ 03 / Reverse sync

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
Flow diagram: Reverse sync: database work orders become Sentra 311 requestsEvery 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work shows up in 311.Every 15 minutesOn a scheduleEvery 15 minutes (workspace time zone)Changed work ordersRead database · PostgreSQLReads from PostgreSQL / PostGIS tablework_ordersShape as a 311 requestMap fieldsShapes each record into 5 fields: description,address, source, category, external_refCreate 311 requestSend records · Sentra 311Creates Service requests in Sentra 311
Reverse sync: database work orders become Sentra 311 requests · 4 steps · a real SentraBridge template
§ FAQ

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.