Sentra 311
Service requests from residents, with staff workflow and a public API. Connector →
SentraBridge knows every Sentra product out of the box: real paths, fields, webhooks with verified signatures, and a sandbox for each. No mapping needed between our own products.
Service requests from residents, with staff workflow and a public API. Connector →
Crew and appointment scheduling for field and counter work. Connector →
Lobby queues and appointments for public counters. Connector →
Agendas, meetings, votes and minutes for councils and boards. Connector →
Websites for public agencies, with an API for publishing. Connector →
Recorder notices and alerts for property owners (SB 255). Connector →
Document accessibility and privacy scans, with an API. Connector →
The connector between all of them, and everything else with an API.
Learn more →Every 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.
Sentra 311 → Accela Civic PlatformWhen Sentra 311 sends request.created, code-enforcement requests become new Accela records. Everything else is ignored.
Sentra 311 → PostgreSQL / PostGISEvery 15 minutes, upserts new and changed Sentra 311 requests into a PostGIS table, with a map point built from latitude and longitude.
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP serverCleans 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 311Every Monday at 7 am, counts last week's closed 311 requests by type and emails the summary.
Accela Civic Platform → Sentra 311Every 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.
SentraBridge adds every Sentra-to-Sentra flow, plus connectors to your other systems.