Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Our productsConnector

Sentra 311 integration with city work order systems

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.

Pre-built connector

Sentra 311

Tier
Pre-built connector
Category
Our products
Sign-in
API token (Bearer)
Paging
cursor
Webhooks
5 events, signatures verified
Sandbox
Yes: practice with made-up data
§ Overview

What connecting Sentra 311 does.

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.

  • Service requests: Read changed requests; create and update status, priority, category, department, assignee and address.
  • Request types: Read, create and update categories and their departments.
  • Replies to residents: Post a reply message on a request.
  • Webhooks: request.created, assigned, status_changed, closed and reopened, with HMAC signatures.
What SentraBridge can do with Sentra 311
resourcereadwritechanges onlyfields
Service requestslist, read onecreate, updateyesID, Request number, Status, Priority, Category, Department…
Request typeslist, read onecreate, update—ID, Name, Department
Replies to residents—create—Request ID, Message

Webhook events: request.created request.assigned request.status_changed request.closed request.reopened

§ Use cases

What cities connect Sentra 311 for.

Potholes to the street crew

Every 15 minutes, new or changed pothole requests create visits for the street repair crew in Sentra Scheduler.

Code complaints to Accela

On request.created, code enforcement requests become Accela records; everything else is ignored.

Triage and routing

Changed requests are cleaned and checked, bad ones go to a data-quality sub-flow, and the rest route by type.

Weekly summary for department heads

Every Monday at 7 am, last week's closed requests are counted by type and emailed.

Nightly backup and export

Requests are written to a dated JSON file in S3 and a CSV on SFTP for other systems.

§ How it works

How to connect Sentra 311

  1. 01Get accessBuild and test flows on the Sentra 311 sandbox with made-up requests.
  2. 02Add the connectionMachine tokens are coming to Sentra 311; until then, use the sandbox.
  3. 03Preview real recordsThen add a Sentra 311 API token for SentraBridge.
  4. 04Turn it onFor webhooks, register the flow's address and signing secret in Sentra 311.
§ Often connected with

Sentra 311 and the rest of city hall.

Systems cities commonly connect with Sentra 311, each with its own connector page.

§ FAQ

Sentra 311 integration questions

Does Sentra 311 support webhooks?

Yes. Sentra 311 sends signed events when requests are created, assigned, change status, close or reopen. SentraBridge checks the signature before reading anything.

How do I send 311 requests to Accela?

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.

Can work done elsewhere close the 311 request?

Yes. Flows read closed Accela records or work orders in the city database and close or update the matching 311 request.

Connect Sentra 311 to the rest.

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