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

Real flows.
Drawn from the product.

Every diagram here is generated from a template that ships with SentraBridge. Open one to see each step explained, then preview it on your own data.

Flow diagram: Publish upcoming CivicCA meetings to the websiteEvery night at 1 am, takes upcoming meetings with a published agenda from CivicCA and adds them as pages on the Sentra CMS website.Nightly at 1 amOn a scheduleEvery night at 1:00 am (workspace timezone)Get meetingsGet records · CivicCAReads Meetings from CivicCAUpcoming, agendapublishedFilterKeeps only records where meeting_date isafter {{ $today }} and agenda_status is publ…Shape as a web pageMap fieldsShapes each record into 5 fields: title, path,type, status, bodyCreate website pageSend records · Sentra CMSCreates Pages in Sentra CMS
Publish upcoming CivicCA meetings to the website · 5 steps · a real SentraBridge template
§ 01

Advanced flows

Branches, sub-flows, lookups and several destinations.

Flow diagram: 311 triage: route every request to the right systemCleans and checks changed 311 requests, sends bad ones to a data-quality sub-flow, checks the city database to see if each is new, then routes new potholes, lights and trees to Scheduler crews, code cases to the ArcGIS map, and the rest to an SFTP file. Changed requests are upserted into the database with map points, and a summary by department is emailed.Every 15 minutesOn a scheduleChanged 311 requestsGet records · Sentra 311Clean and checkApply rulesData quality alertRun another flowCount by departmentSummarizeAlready in the database?Look up in database · PostgreSQLEmail operationsSend emailNew request?If / elseCrew work?If / elseName like the columnsMap fieldsShape as a crew visitMap fieldsCode enforcement?If / elseUpdate the database copyWrite to database · PostgreSQLCreate Scheduler visitSend records · Sentra SchedulerMap attributesMap fieldsEverything else to SFTPWrite file · SFTPMake map pointMake map pointAdd to the code-casemapSend records · ArcGISInvalidYesYesNoYesNoNo
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP server

311 triage: route every request to the right system

Cleans and checks changed 311 requests, sends bad ones to a data-quality sub-flow, checks the city database to see if each is new, then…

18 steps · Step by step →
Flow diagram: Meter reads from AMI to utility billing with zero-read checkEvery morning, reads the Neptune 360 export from the SFTP folder. Reads that look wrong (35 days with no flow, a skipped read or a read error) go to the meter team and become re-read service orders; good reads load into utility billing.Daily at 5 amOn a scheduleRead the AMI exportRead files · SFTPTo meter read fieldsMap fieldsZero or missing read?If / elseFields for: load the readMap fieldsFields for: open a re-readorderMap fieldsLoad the readSend records · Utility billingOpen a re-read orderSend records · Utility billingTell the meter teamSend emailNoYesYes
SFTP server → Utility billing (CIS)

Meter reads from AMI to utility billing with zero-read check

Every morning, reads the Neptune 360 export from the SFTP folder. Reads that look wrong (35 days with no flow, a skipped read or a read…

9 steps · Step by step →
Flow diagram: File CivicCA agendas and minutes in LaserficheEvery hour, files each newly published CivicCA agenda and set of minutes in the city's Laserfiche repository, in the folder for that board, with meeting metadata. Each municipality sets its own boards-to-folders value map; boards without a folder go to the data-quality alert instead of being misfiled.Every hourOn a scheduleChanged meetingsGet records · CivicCAAgenda publishedFilterFind the board's folderApply rulesData quality alertRun another flowFile the agendaTransfer file · LaserficheMinutes ready?If / elseFile the minutesTransfer file · LaserficheInvalidYes
CivicCA → Laserfiche Cloud

File CivicCA agendas and minutes in Laserfiche

Every hour, files each newly published CivicCA agenda and set of minutes in the city's Laserfiche repository, in the folder for that board,…

8 steps · Step by step →
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
Sentra 311 → SentraQueue → PostgreSQL / PostGIS → SFTP server

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,…

13 steps · Step by step →
Flow diagram: Daily payment file from Paymentus posts to utility billingEvery weekday morning, reads Paymentus's payment file from the SFTP folder, keeps accepted payments, checks each account exists in utility billing, and posts the payments. Payments for unknown accounts are emailed to the billing office instead of posted.Weekdays at 6:30 amOn a scheduleRead the Paymentus fileRead files · SFTPAccepted payments onlyFilterUtility billing accountsGet records · Utility billingTo utility billing fieldsMap fieldsFind the accountJoinAccount found?If / elseFields for: post thepaymentMap fieldsEmail unknown accountsSend emailPost the paymentSend records · Utility billingYesNo
SFTP server → Utility billing (CIS)

Daily payment file from Paymentus posts to utility billing

Every weekday morning, reads Paymentus's payment file from the SFTP folder, keeps accepted payments, checks each account exists in utility…

10 steps · Step by step →
Flow diagram: Permit pipeline: map issued, report finaled, file expiredNightly, reads changed permits with a SQL query, cleans and checks them, then puts issued permits on the ArcGIS map, emails building a total of finaled permits by type, and writes expired permits to a CSV file on SFTP.Nightly at 2 amOn a scheduleChanged permitsRead database · PostgreSQLClean and checkApply rulesIssued?If / elseMap attributesMap fieldsFinaled?If / elseMake map pointMake map pointTotal by typeSummarizeExpired?If / elseAdd to the permit mapSend records · ArcGISEmail buildingSend emailExpired permits to SFTPWrite file · SFTPYesNoYesNoYes
PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP server

Permit pipeline: map issued, report finaled, file expired

Nightly, reads changed permits with a SQL query, cleans and checks them, then puts issued permits on the ArcGIS map, emails building a…

12 steps · Step by step →
§ 02

Everyday flows

One source, one destination, done well.

Flow diagram: New pothole requests become Scheduler visitsEvery 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.Every 15 minutesOn a scheduleChanged 311 requestsGet records · Sentra 311Open potholesFilterShape as a visitMap fieldsCreate Scheduler visitSend records · Sentra Scheduler
Sentra 311 → Sentra Scheduler

New pothole requests become Scheduler visits

Every 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.

5 steps · Step by step →
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
Sentra 311 → Accela Civic Platform

311 code-enforcement requests become Accela records

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

4 steps · Step by step →
Flow diagram: Copy 311 requests into the city database, with map pointsEvery 15 minutes, upserts new and changed Sentra 311 requests into a PostGIS table, with a map point built from latitude and longitude.Every 15 minutesOn a scheduleChanged 311 requestsGet records · Sentra 311Name fields like thecolumnsMap fieldsUpsert intoservice_requestsWrite to database · PostgreSQL
Sentra 311 → PostgreSQL / PostGIS

Copy 311 requests into the city database, with map points

Every 15 minutes, upserts new and changed Sentra 311 requests into a PostGIS table, with a map point built from latitude and longitude.

4 steps · Step by step →
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 scheduleGet 311 requestsGet records · Sentra 311Closed in the last 7 daysFilterCount by request typeSummarizeEmail department headsSend email
Sentra 311

Weekly 311 summary for department heads

Every Monday at 7 am, counts last week's closed 311 requests by type and emails the summary.

5 steps · Step by step →
Flow diagram: Closed Accela records close their 311 requestsEvery 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.Every 15 minutesOn a scheduleChanged Accela recordsGet records · AccelaClosed, from 311FilterClosing updateMap fieldsClose 311 requestSend records · Sentra 311
Accela Civic Platform → Sentra 311

Closed Accela records close their 311 requests

Every 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.

5 steps · Step by step →
Flow diagram: Make a Laserfiche folder for each new Accela permitEvery hour, creates a folder in Laserfiche for each new building record in Accela, named with the record number and address.Every hourOn a scheduleChanged Accela recordsGet records · AccelaBuilding recordsFilterFolder nameMap fieldsCreate folderSend records · Laserfiche
Accela Civic Platform → Laserfiche Cloud

Make a Laserfiche folder for each new Accela permit

Every hour, creates a folder in Laserfiche for each new building record in Accela, named with the record number and address.

5 steps · Step by step →
Flow diagram: Publish agendas on the website after the clerk approvesEvery morning, finds upcoming meetings with a published agenda in CivicCA and asks the city clerk to approve them. Approved agendas become pages on the Sentra CMS website; nothing is published without a yes.Weekdays at 8 amOn a scheduleGet meetingsGet records · CivicCAUpcoming, agendapublishedFilterClerk approvesWait for approvalShape as a web pageMap fieldsCreate website pageSend records · Sentra CMS
CivicCA → Sentra CMS

Publish agendas on the website after the clerk approves

Every morning, finds upcoming meetings with a published agenda in CivicCA and asks the city clerk to approve them. Approved agendas become…

6 steps · Step by step →
Flow diagram: Nightly backup: Sentra 311 requests to S3Every night, copies all Sentra 311 requests to a dated JSON file in the city's own S3 bucket. The backup lives in the city's storage; SentraBridge keeps nothing.Nightly at 1:30 amOn a scheduleAll 311 requestsGet records · Sentra 311Dated JSON fileWrite file · Amazon S3Tell ITSend email
Sentra 311 → Amazon S3 / S3-compatible

Nightly backup: Sentra 311 requests to S3

Every night, copies all Sentra 311 requests to a dated JSON file in the city's own S3 bucket. The backup lives in the city's storage;…

4 steps · Step by step →
Flow diagram: Nightly backup: a database table to CSV in S3Every night, exports a city database table (here: permits) to a dated CSV file in S3, so there's always a plain-text copy outside the database.Nightly at 2:30 amOn a scheduleWhole permits tableRead database · PostgreSQLDated CSV fileWrite file · Amazon S3
PostgreSQL / PostGIS → Amazon S3 / S3-compatible

Nightly backup: a database table to CSV in S3

Every night, exports a city database table (here: permits) to a dated CSV file in S3, so there's always a plain-text copy outside the…

3 steps · Step by step →
Flow diagram: Load the bank's daily payment file into the city databaseEvery morning, reads new payment CSV files from the bank's SFTP folder, cleans and checks them, loads them into a database table, and archives the files. Bad rows are emailed to finance.Weekdays at 6 amOn a scheduleRead payment filesRead files · SFTPClean and checkApply rulesLoad intoutility_paymentsWrite to database · PostgreSQLEmail bad rows tofinanceSend emailInvalid
SFTP server → PostgreSQL / PostGIS

Load the bank's daily payment file into the city database

Every morning, reads new payment CSV files from the bank's SFTP folder, cleans and checks them, loads them into a database table, and…

5 steps · Step by step →
Flow diagram: Publish upcoming CivicCA meetings to the websiteEvery night at 1 am, takes upcoming meetings with a published agenda from CivicCA and adds them as pages on the Sentra CMS website.Nightly at 1 amOn a scheduleGet meetingsGet records · CivicCAUpcoming, agendapublishedFilterShape as a web pageMap fieldsCreate website pageSend records · Sentra CMS
CivicCA → Sentra CMS

Publish upcoming CivicCA meetings to the website

Every night at 1 am, takes upcoming meetings with a published agenda from CivicCA and adds them as pages on the Sentra CMS website.

5 steps · Step by step →
Flow diagram: Data quality alert (sub-flow)A reusable sub-flow: other flows hand it the records that failed their checks, and it emails the data team a summary with a CSV attached.Records from anotherflowRun by handFirst 500Keep firstEmail the data teamSend email

Data quality alert (sub-flow)

A reusable sub-flow: other flows hand it the records that failed their checks, and it emails the data team a summary with a CSV attached.

3 steps · Step by step →
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
PostgreSQL / PostGIS → Sentra 311

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…

4 steps · Step by step →
Flow diagram: EnerGov issued permits to ArcGISEvery night, reads permits issued or changed in EnerGov since the last run and adds them to the permits map layer in ArcGIS.Nightly at 2 amOn a schedulePermits from EnerGovGet records · Tyler EnerGovIssued onlyFilterTo layer fieldsMap fieldsMake map pointMake map pointAdd to the map layerSend records · ArcGIS
Tyler EnerGov → Esri ArcGIS feature layer

EnerGov issued permits to ArcGIS

Every night, reads permits issued or changed in EnerGov since the last run and adds them to the permits map layer in ArcGIS.

6 steps · Step by step →
Flow diagram: Munis paid checks to the bank positive pay fileEvery weekday afternoon, reads the AP checks Munis issued and writes the bank's positive pay file to the SFTP outbox, so the bank only clears checks the city actually wrote.Weekdays at 4 pmOn a scheduleAP invoices from MunisGet records · MunisPaid by checkFilterPositive pay fieldsMap fieldsWrite the positive pay fileWrite file · SFTP
Tyler Enterprise ERP (Munis) → SFTP server

Munis paid checks to the bank positive pay file

Every weekday afternoon, reads the AP checks Munis issued and writes the bank's positive pay file to the SFTP outbox, so the bank only…

5 steps · Step by step →
Flow diagram: New hires from NEOGOV to Munis (employee and payee vendor)Every morning, reads yesterday's hires from NEOGOV and creates each one in Munis: an employee record for payroll, and a payee vendor so expense reimbursements can be paid.Daily at 6 amOn a scheduleRecent hires in NEOGOVGet records · NEOGOVFields for: create themunis employeeMap fieldsFields for: create thepayee vendorMap fieldsCreate the MunisemployeeSend records · MunisCreate the payee vendorSend records · Munis
NEOGOV → Tyler Enterprise ERP (Munis)

New hires from NEOGOV to Munis (employee and payee vendor)

Every morning, reads yesterday's hires from NEOGOV and creates each one in Munis: an employee record for payroll, and a payee vendor so…

6 steps · Step by step →
Flow diagram: Nightly 311 export as a CSV file on SFTPEvery night, writes yesterday's changed Sentra 311 requests to a dated CSV file in an SFTP folder for another system to pick up.Nightly at 11:30 pmOn a scheduleChanged 311 requestsGet records · Sentra 311Columns for the fileMap fieldsWrite CSVWrite file · SFTP
Sentra 311 → SFTP server

Nightly 311 export as a CSV file on SFTP

Every night, writes yesterday's changed Sentra 311 requests to a dated CSV file in an SFTP folder for another system to pick up.

4 steps · Step by step →
Flow diagram: Post severe weather alerts on the city websiteEvery 15 minutes, takes severe or extreme National Weather Service alerts for your state and posts them as website alerts in Sentra CMS.Every 15 minutesOn a scheduleActive alerts for CAGet records · Weather ServiceSevere or extremeFilterShape as a website alertMap fieldsCreate website alertSend records · Sentra CMS
National Weather Service alerts → Sentra CMS

Post severe weather alerts on the city website

Every 15 minutes, takes severe or extreme National Weather Service alerts for your state and posts them as website alerts in Sentra CMS.

5 steps · Step by step →
Flow diagram: Publish OpenGov permits to the open-data portalNightly, upserts changed OpenGov permit records into a Socrata / Tyler Data & Insights dataset.Nightly at 3 amOn a scheduleChanged OpenGovrecordsGet records · OpenGovPublic fields onlyMap fieldsUpsert into the datasetSend records · Socrata
OpenGov Permitting & Licensing → Socrata / Tyler Data & Insights

Publish OpenGov permits to the open-data portal

Nightly, upserts changed OpenGov permit records into a Socrata / Tyler Data & Insights dataset.

4 steps · Step by step →
Flow diagram: Publish issued permits to an ArcGIS map layerNightly, reads permits issued since the last run from the city database and adds them as points on an ArcGIS feature layer.Nightly at 2 amOn a scheduleIssued permitsRead database · PostgreSQLMake map pointMake map pointAdd to the layerSend records · ArcGIS
PostgreSQL / PostGIS → Esri ArcGIS feature layer

Publish issued permits to an ArcGIS map layer

Nightly, reads permits issued since the last run from the city database and adds them as points on an ArcGIS feature layer.

4 steps · Step by step →
Flow diagram: Follow up with SentraQueue no-showsEvery hour, emails visitors who were called but didn't show, with a link to rejoin the line.Every hourOn a scheduleChanged visitsGet records · SentraQueueNo-shows with an emailFilterEmail each visitorSend email
SentraQueue

Follow up with SentraQueue no-shows

Every hour, emails visitors who were called but didn't show, with a link to rejoin the line.

4 steps · Step by step →
Flow diagram: Salesforce web cases become Sentra 311 requestsEvery 15 minutes, turns new Salesforce cases from the web into Sentra 311 service requests.Every 15 minutesOn a scheduleChanged casesGet records · SalesforceNew, from the webFilterShape as a 311 requestMap fieldsCreate 311 requestSend records · Sentra 311
Salesforce → Sentra 311

Salesforce web cases become Sentra 311 requests

Every 15 minutes, turns new Salesforce cases from the web into Sentra 311 service requests.

5 steps · Step by step →
Flow diagram: Utility billing vs general ledger daily balance checkEvery morning, compares each day's payment total in utility billing with the cash receipts journal entry in Munis. Days that don't match, or have no journal entry, are emailed to finance with the difference.Weekdays at 7 amOn a scheduleUtility billing daily totalsGet records · Utility billingMunis journal entriesGet records · MunisCash posted per dayMap fieldsBilling vs ledgerReconcileEmail finance thedifferencesSend email
Utility billing (CIS) → Tyler Enterprise ERP (Munis)

Utility billing vs general ledger daily balance check

Every morning, compares each day's payment total in utility billing with the cash receipts journal entry in Munis. Days that don't match,…

6 steps · Step by step →

Want one of these on your data?

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