Re-keying between systems
Staff copy 311 requests into permitting, permit numbers into GIS and agendas onto the website by hand, and the copies drift apart.
Cities & townsWho we serve
Every department's system.
Finally talking.
311, permitting, finance, GIS, the website and the records repository each came from a different vendor. SentraBridge moves records between them on a schedule or as they happen, without keeping a copy.
§ The problem
What gets in the way.
Integrations nobody can see
Scripts written years ago run on a server somewhere. When one stops, nobody knows until a resident or a department calls.
Another copy to protect
Many integration tools keep their own copy of what they move, which becomes one more place resident data has to be secured and retained.
§ How it works
How it works for cities & towns
- 01ConnectAdd 311, permitting, GIS and the database as connections.
- 02Draw the flowRead, clean, decide and write, on one canvas.
- 03PreviewCheck real records at each step; nothing is written.
- 04Turn it onOn a schedule, by webhook, or on database changes.
- 05Watch itRun history, alerts and replay when something fails.
§ What you get
Built for cities & towns.
Draw it, don't code it
Build flows on a drag-and-drop canvas: read records, clean and check them, decide, and write them somewhere else.
Learn more →Pre-built for city systems
Sentra products, Accela, OpenGov, Laserfiche, Esri ArcGIS, Microsoft 365 and more, plus any REST API or OpenAPI file.
Learn more →See the data first
Preview real records at every step before anything is written. The preview never sends or stores anything.
Learn more →On your schedule
Run by hand, on a schedule in the city's time zone, when a system calls in, or when database rows change.
Learn more →Know what ran
Run history, failure emails, replay of failed records by ID, and a monitoring dashboard for every flow.
Learn more →Pass-through by design
Records live in memory only while a flow runs. History keeps counts, timings and record IDs, never contents.
Learn more →§ Examples
Flows that fit.
Generated from SentraBridge's ready-made templates.
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP server
311 triage: route every request to the right system
Cleans 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…
Sentra 311 → Accela Civic Platform311 code-enforcement requests become Accela records
When Sentra 311 sends request.created, code-enforcement requests become new Accela records. Everything else is ignored.
CivicCA → Sentra CMSPublish upcoming CivicCA meetings to the website
Every night at 1 am, takes upcoming meetings with a published agenda from CivicCA and adds them as pages on the Sentra CMS website.
PostgreSQL / PostGIS → Esri ArcGIS feature layerPublish issued permits to an ArcGIS map layer
Nightly, reads permits issued since the last run from the city database and adds them as points on an ArcGIS feature layer.
§ Systems
Systems you likely run.
Each links to its connector page. Not listed? Any REST API, OpenAPI file, database or SFTP server works.
Sentra 311
CivicCA§ FAQ
Questions, answered
Do we need a developer to use it?
No. Flows are drawn on a canvas, and ready-made templates cover common city integrations. Staff who are comfortable with spreadsheets can map fields and set rules. CSP can also build flows with you as an assisted service.
Does SentraBridge keep a copy of our records?
No. Records pass through in memory while a flow runs and are dropped when it ends. Run history keeps counts, timings and record IDs only, so there's no third copy to secure, retain or produce.
We don't use any Sentra products. Does it still work?
Yes. SentraBridge is sold standalone. It connects any system with an API, plus SQL Server, PostgreSQL and MySQL databases, SFTP files and ArcGIS layers.
See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.