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

Reverse sync: database work orders become Sentra 311 requests

Every 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work shows up in 311.

This flow

4 steps

StartsOn a schedule
SystemsPostgreSQL / PostGIS, Sentra 311
Branches0
Stored recordsNone: pass-through
§ The flow

The whole flow, as it appears on the canvas.

Scroll sideways on small screens. Colors show the kind of step: start, read, change, decide, write.

Flow diagram: Reverse sync: database work orders become Sentra 311 requestsEvery 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work shows up in 311.Every 15 minutesOn a scheduleChanged work ordersRead database · PostgreSQLShape as a 311 requestMap fieldsCreate 311 requestSend records · Sentra 311
StartReadFilesDatabaseChangeDecideWriteAct
§ Step by step

What each step does.

  1. 01 · Start · On a schedule

    Every 15 minutes

    • Every 15 minutes (workspace time zone)

    Then: Changed work orders

  2. 02 · Database · Read database · PostgreSQL / PostGIS

    Changed work orders

    • Reads from PostgreSQL / PostGIS table work_orders
    • Row ID column: ref (used for replay and lineage)

    Then: Shape as a 311 request

  3. 03 · Change · Map fields

    Shape as a 311 request

    • Shapes each record into 5 fields: description, address, source, category, external_ref

    Then: Create 311 request

  4. 04 · Write · Send records · Sentra 311

    Create 311 request

    • Creates Service requests in Sentra 311
§ Systems

Connectors used

Swap any of them for another system with the same kind of data.

Run this flow on your systems.

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