Potholes to the street crew
Every 15 minutes, new or changed pothole requests create visits for the street repair crew in Sentra Scheduler.
Sentra 311 is a service request system for residents and staff: potholes, streetlights, code complaints and more, from the web, phone and mobile apps. It is made by the same company family as SentraBridge.
The connector is pre-built with signed webhooks for created, assigned, status-changed, closed and reopened requests. Flows route each request to the system that does the work and post replies to residents when it's done. Request details pass through SentraBridge and are not kept.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Service requests | list, read one | create, update | yes | ID, Request number, Status, Priority, Category, Department… |
| Request types | list, read one | create, update | — | ID, Name, Department |
| Replies to residents | — | create | — | Request ID, Message |
Webhook events: request.created request.assigned request.status_changed request.closed request.reopened
Every 15 minutes, new or changed pothole requests create visits for the street repair crew in Sentra Scheduler.
On request.created, code enforcement requests become Accela records; everything else is ignored.
Changed requests are cleaned and checked, bad ones go to a data-quality sub-flow, and the rest route by type.
Every Monday at 7 am, last week's closed requests are counted by type and emailed.
Requests are written to a dated JSON file in S3 and a CSV on SFTP for other systems.
When 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…
Systems cities commonly connect with Sentra 311, each with its own connector page.
Yes. Sentra 311 sends signed events when requests are created, assigned, change status, close or reopen. SentraBridge checks the signature before reading anything.
Start a flow from the request.created webhook, keep code enforcement types, map fields to an Accela record and create it. A ready template does this.
Yes. Flows read closed Accela records or work orders in the city database and close or update the matching 311 request.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.