Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Vendors & managed service providersWho we serve

Serve many agencies.
Keep every one apart.

If you support several cities, counties or districts, SentraBridge gives each its own workspace. Publish a shared template once, roll it out to many clients, and see every client's runs from one place.

Flow diagram: Data quality alert (sub-flow)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.Records from anotherflowRun by handStarts by hand, or when another flow hands itrecords (a sub-flow)First 500Keep firstKeeps the first 500 recordsEmail the data teamSend emailEmails [email protected]:“{{count}} records failed checks”
Data quality alert (sub-flow) · 3 steps · a real SentraBridge template
§ The problem

What gets in the way.

The same integration, many times

Every client needs the same flow with small differences, and copies drift apart once deployed.

Mixing client data

Staff who work for several agencies must never let one client's connections or records reach another.

Who's broken right now?

Failures across many clients are hard to spot until a client calls.

§ How it works

How it works for vendors & msps

  1. 01Build onceDesign and preview the flow in your own workspace.
  2. 02PublishPublish it as a shared template.
  3. 03Roll outInstall it into each client's workspace.
  4. 04Fit each clientEach client sets its own connections and value maps.
  5. 05UpdateClients get a notice when the template changes.
§ Examples

Flows that fit.

Generated from SentraBridge's ready-made templates.

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
§ Systems

Systems you likely run.

Each links to its connector page. Not listed? Any REST API, OpenAPI file, database or SFTP server works.

§ FAQ

Questions, answered

Can one person work across several clients?

Yes. Staff switch between client workspaces, and nothing crosses over between them.

How do template updates reach clients?

When you update a shared template, clients that use it get an update notice.

Can clients see each other?

No. Each workspace's connections, flows, code tables, people and history are invisible to other workspaces.

See your own systems connected.

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