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

Complaints become cases.
Cases show up on the map.

Code-enforcement requests from 311 become Accela records, open cases appear on the ArcGIS map, and closing the case closes the resident's request.

Request a demoSee live examples
Flow diagram: Closed Accela records close their 311 requestsEvery 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.Every 15 minutesOn a scheduleEvery 15 minutes (workspace time zone)Changed Accela recordsGet records · AccelaReads Records from Accela Civic PlatformClosed, from 311FilterKeeps only records where status.value is oneof Closed, Complete and customId starts wi…Closing updateMap fieldsShapes each record into 2 fields: status,request_numberClose 311 requestSend records · Sentra 311Updates Service requests in Sentra 311
Closed Accela records close their 311 requests · 5 steps · a real SentraBridge template
§ The problem

What gets in the way.

Double entry

Officers re-key complaints from 311 into the case system.

No map of open cases

Seeing where cases cluster means exporting and plotting by hand.

Residents left waiting

Closing the case doesn't tell the resident who reported it.

§ How it works

How it works for code enforcement

  1. 01Complaint filedSentra 311 sends request.created.
  2. 02Code enforcement?Everything else is ignored.
  3. 03ShapeAs an Accela record.
  4. 04Create the caseIn Accela.
§ What you get

Built for code enforcement.

311 to Accela

Code-enforcement requests become Accela records the moment 311 calls in.

Learn more →

Cases on the map

Map attributes and points are added to an ArcGIS code-case layer.

Learn more →

Closures back to 311

Closed Accela records close the matching 311 request.

Learn more →
§ Examples

Flows that fit.

Generated from SentraBridge's ready-made templates.

Flow diagram: Closed Accela records close their 311 requestsEvery 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.Every 15 minutesOn a scheduleChanged Accela recordsGet records · AccelaClosed, from 311FilterClosing updateMap fieldsClose 311 requestSend records · Sentra 311
Closed Accela records close their 311 requests · 5 steps · a real SentraBridge template
Sentra 311 → Accela Civic Platform

311 code-enforcement requests become Accela records

When Sentra 311 sends request.created, code-enforcement requests become new Accela records. Everything else is ignored.

4 steps · View the flow →Accela Civic Platform → Sentra 311

Closed Accela records close their 311 requests

Every 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.

5 steps · View the flow →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…

18 steps · View the flow →
§ 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

Do we need to use Accela?

No. OpenGov has a pre-built connector, and any case system with an API can be connected.

Will every city's Accela setup work?

Record types and statuses differ per city, so templates are checked against your setup in preview before they're turned on.

Are complainant details stored?

No. Records pass through in memory only.

See your own systems connected.

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

Request a demoBrowse live examples