Requests re-keyed into work systems
Dispatchers copy 311 requests into the crew schedule by hand.
Potholes, streetlights and trees reported through 311 become crew visits automatically, and work orders created by phone or in the database show up in 311.
Dispatchers copy 311 requests into the crew schedule by hand.
Work orders taken by phone never appear in the 311 system residents check.
Numbers come from several systems and are compiled by hand each week.
New pothole requests become Sentra Scheduler visits for the street repair crew.
Learn more →Work orders created or changed in the city database become 311 requests.
Learn more →Count last week's closed requests by type and email department heads every Monday.
Learn more →Generated from SentraBridge's ready-made templates.
Every 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.
PostgreSQL / PostGIS → Sentra 311Every 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work…
Sentra 311Every Monday at 7 am, counts last week's closed 311 requests by type and emails the summary.
Sentra 311 → SentraQueue → PostgreSQL / PostGIS → SFTP serverWeekdays at 7 am, reads 311 requests, SentraQueue lobby visits and database work orders, puts them in one shape, combines and sorts them, emails a…
Each links to its connector page. Not listed? Any REST API, OpenAPI file, database or SFTP server works.
Yes. Cityworks (Trimble Unity) has a pre-built connector for service requests and work orders.
Yes. A flow can read changed work orders and update the matching 311 request.
Yes. Database change triggers use a changed-column watermark, SQL Server Change Tracking or PostgreSQL LISTEN/NOTIFY.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.