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

Morning operations digest from three systems

Weekdays at 7 am, reads 311 requests, SentraQueue lobby visits and database work orders, puts them in one shape, combines and sorts them, emails a count of open items by source, and archives the whole list as JSON on SFTP.

Try it on your dataAll examples
This flow

13 steps

StartsOn a schedule
SystemsSentra 311, SentraQueue, PostgreSQL / PostGIS, SFTP server
Branches1
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: Morning operations digest from three systemsWeekdays at 7 am, reads 311 requests, SentraQueue lobby visits and database work orders, puts them in one shape, combines and sorts them, emails a count of open items by source, and archives the whole list as JSON on SFTP.Weekdays at 7 amOn a schedule311 requestsGet records · Sentra 311Lobby visitsGet records · SentraQueueWork ordersRead database · PostgreSQLAs one shapeMap fieldsAs one shapeMap fieldsAs one shapeMap fieldsCombineCombineNewest firstSortStill open?If / elseArchive as JSONWrite file · SFTPCount by sourceSummarizeEmail the digestSend emailYes
StartReadFilesDatabaseChangeDecideWriteAct
§ Step by step

What each step does.

  1. 01 · Start · On a schedule

    Weekdays at 7 am

    • Weekdays at 7:00 am (workspace time zone)

    Then: 311 requests; Lobby visits; Work orders

  2. 02 · Read · Get records · Sentra 311

    311 requests

    • Reads Service requests from Sentra 311
    • At most 500 records per run

    Then: As one shape

  3. 03 · Read · Get records · SentraQueue

    Lobby visits

    • Reads Visits (tickets) from SentraQueue
    • At most 500 records per run

    Then: As one shape

  4. 04 · Database · Read database · PostgreSQL / PostGIS

    Work orders

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

    Then: As one shape

  5. 05 · Change · Map fields

    As one shape

    • Shapes each record into 5 fields: source, ref, status, area, updated

    Then: Combine

  6. 06 · Change · Map fields

    As one shape

    • Shapes each record into 5 fields: source, ref, status, area, updated

    Then: Combine

  7. 07 · Change · Map fields

    As one shape

    • Shapes each record into 5 fields: source, ref, status, area, updated

    Then: Combine

  8. 08 · Decide · Combine

    Combine

    • Combines the records from every incoming wire into one list

    Then: Newest first

  9. 09 · Change · Sort

    Newest first

    • Sorts by updated, newest / largest first

    Then: Still open?; Archive as JSON

  10. 10 · Decide · If / else

    Still open?

    • Yes when status is one of open, in_progress, waiting, called

    Then: Yes → Count by source

  11. 11 · Files · Write file · SFTP server

    Archive as JSON

    • Writes JSON file operations-digest-{{ $today }}.json to outbox
    • One file with every record
  12. 12 · Change · Summarize

    Count by source

    • Counts records by source

    Then: Email the digest

  13. 13 · Act · Send email

    Email the digest

    • Emails [email protected]: “Good morning: open items across 311, the lobby and work orders”
    • One summary email
§ Systems

Connectors used

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

§ Next

Keep exploring

SolutionOperations reportingExampleNew pothole requests become Scheduler visitsExample311 code-enforcement requests become Accela recordsExampleCopy 311 requests into the city database, with map points

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.

Request a demoBrowse live examples