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

311 code-enforcement requests become Accela records

When Sentra 311 sends request.created, code-enforcement requests become new Accela records. Everything else is ignored.

This flow

4 steps

StartsWhen a system calls in
SystemsSentra 311, Accela Civic Platform
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: 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
StartReadFilesDatabaseChangeDecideWriteAct
§ Step by step

What each step does.

  1. 01 · Start · When a system calls in

    Sentra 311 calls in

    • Runs the moment the other system calls this flow's webhook address
    • The message's signature can be checked before anything is read
    • Records are taken from data in the message

    Then: Code enforcement?

  2. 02 · Decide · If / else

    Code enforcement?

    • Yes when department is Code Enforcement

    Then: Yes → Shape as an Accela record

  3. 03 · Change · Map fields

    Shape as an Accela record

    • Shapes each record into 4 fields: type.value, description, addresses.0.streetAddress, customId

    Then: Create Accela record

  4. 04 · Write · Send records · Accela Civic Platform

    Create Accela record

    • Creates Records in Accela Civic Platform
§ 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.