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

Run it when it matters.
Not just every 15 minutes.

Flows run by hand, on a schedule in the city's time zone, when a system calls in, or when database rows change. Webhooks are verified before a single record is read.

Four ways to start a flowA flow can start by hand, on a schedule, when a system calls in, or when database rows change.Run by handStartWeekdays at 6 amOn a scheduleSentra 311 calls inSignature checkedRows changedDatabase changeGet the recordsGet recordsSend them onSend records
Every flow has one start step; swap it any time without redrawing the rest.
§ 01 / Schedules

Cron, in your time zone.

Every N minutes, hourly, nightly, weekdays only, or a cron expression, all in the workspace's time zone. The next run times are shown before you save, and runs never overlap: if one is still going, the next waits.

  • Down to every minute
  • Run now and pause at any time
  • Only records changed since the last good run
Flow diagram: Weekly 311 summary for department headsEvery Monday at 7 am, counts last week's closed 311 requests by type and emails the summary.Mondays at 7 amOn a scheduleMondays at 7:00 am (workspace time zone)Get 311 requestsGet records · Sentra 311Reads Service requests from Sentra 311Closed in the last 7 daysFilterKeeps only records where status is closedand closed_at is within the last N days 7Count by request typeSummarizeCounts records by categoryEmail department headsSend emailEmails[email protected]: “31…
Weekly 311 summary for department heads · 5 steps · a real SentraBridge template
§ 02 / Webhooks

When a system calls in.

Each webhook flow gets its own address. Signatures are verified for every Sentra product, plus generic HMAC and shared-token checks for other systems. Webhook flows run inside the request: the message is never put on a queue with data in it.

  • List and ID paths for batched messages
  • Signing secrets encrypted at rest
  • Bad signatures are refused and logged
Flow diagram: 311 code-enforcement requests become Accela recordsWhen Sentra 311 sends request.created, code-enforcement requests become new Accela records. Everything else is ignored.Sentra 311 calls inWhen a system calls inCode enforcement?If / elseShape as an AccelarecordMap fieldsCreate Accela recordSend records · AccelaYes
311 code-enforcement requests become Accela records · 4 steps · a real SentraBridge template
§ 03 / Database changes

When rows change.

Start a flow when rows in a city database change, three ways: polling a changed-time column with a watermark, SQL Server Change Tracking, or PostgreSQL LISTEN/NOTIFY. Only the IDs and times are tracked, never copies of the rows.

  • Pick the method your database supports
  • Watermark advances only after a good run
  • Pairs with reverse sync to APIs
work_orders · changed since 2026-11-10 06:002 rows to send
idtitleupdated_at
1042Pothole on Elm St2026-11-09 08:14
1043Streetlight out2026-11-09 09:02
1044Graffiti, 5th Ave2026-11-10 06:41changed
1039Sidewalk trip hazard2026-11-10 07:03changed
Watermark column · SQL Server Change Tracking · PostgreSQL LISTEN/NOTIFY
Illustration: only rows changed since the last good run are read.
§ FAQ

Questions, answered

What if a system has no webhooks?

Poll it. Accela, for example, has no webhooks, so SentraBridge reads records changed since the last good run (updateDateFrom) on a schedule as often as every minute.

Do two runs ever overlap?

No. A scheduled run waits if the previous one hasn't finished.

See your own systems connected.

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