Clean data in.
Clean data out.
Apply rules cleans and checks each record, with Valid and Invalid outputs. Value maps are code tables that translate one system's codes into another's, kept per client.
| phone | zip | status |
|---|---|---|
| (559) 251.7767 | 93727-1234 | CLSD |
| 5592517767 | 93727 | OPEN |
| 9372 | INSP |
| phone | zip | status | |
|---|---|---|---|
| 559-251-7767 | 93727 | Closed | Valid |
| 559-251-7767 | 93727 | Open | Valid |
| 9372 | Inspection | Invalid: ZIP |
Fix what you can. Catch what you can't.
Rules run in order on each record: trim and collapse spaces, format phones and dates, copy fields, require values, check numbers. Records that fail a check leave by the Invalid output, so they can be emailed, handed to a sub-flow or dropped, instead of landing as junk.
- 17 rule operators, from required to is a number
- Messages per rule: 'No address', 'No map location'
- Invalid records carry the reason with them
The code tables behind clean integrations.
One system says CLSD, the other wants Closed. One department is Public Works, finance calls it PW. A value map holds those pairs, with a fallback for anything unknown: keep it, use a default, or treat it as invalid.
- Per-workspace: each municipality sets its own
- Reused across flows and templates
- Board-to-folder maps for Laserfiche filing
| from (CivicCA board) | to (Laserfiche folder) |
|---|---|
| Planning Commission | /Clerk/Agendas/Planning Commission |
| City Council | /Clerk/Agendas/City Council |
| Parks & Recreation Commission | /Clerk/Agendas/Parks |
| (no match) | → data-quality alert |
See it in real flows.
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, with…
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP server311 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 routes new…
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.
Questions, answered
Where do value maps live?
In the client's workspace. A shared template can ship with a starter map, and each municipality edits its own entries.
What happens to invalid records?
You choose: route them out the Invalid output (to an email, sub-flow or file), or drop them. They're never silently sent.
See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.