Automated Census New Sync Setup Reviews
Every morning, WebRun opens Census, finds the syncs created since yesterday, checks each one's source model, destination object, field mappings, and match key against your setup checklist, drafts a Twilio text when a mapping looks wrong, and posts the review to Microsoft Teams before the sync writes at full volume.
How do I review a new data sync before it writes to production?
WebRun opens Census every morning and reviews the syncs created since yesterday, checking each one's source model, destination, match key, and field mappings against your setup checklist. It drafts a Twilio alert for your approval on anything risky and posts the full review to Microsoft Teams before bad rows reach the CRM.
- A wrong mapping is caught before bad rows reach the CRM
- Every new sync gets the same checklist, not an ad hoc glance
- Rejected rows from a first run are surfaced the next morning
Built for data engineers · analytics engineers · revenue operations · data platform teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.getcensus.comin a real browser with your saved login - no setup, no API keys. -
1
Census - review newly created syncs
getcensus.com
WebRun opens Census to review newly created syncs. - Open Census and list the syncs created since the previous run, with their source, model, and destination
- For each sync record the sync behaviour, the match key, and every field mapping with its source and destination field
- Read the sync history to see whether it has run yet, and capture any rejected rows from that first run
Done when Every new sync has its behaviour, match key, field mappings, and first-run result captured.
-
2
Twilio - draft an alert on a risky mapping
twilio.com
WebRun opens Twilio to draft an alert on a risky mapping. - Draft a short SMS for any sync missing a match key, mapping a field to a mismatched type, or already rejecting rows
- Name the sync, the destination, and the exact problem so it can be paused before the next run
- Queue the message for your approval. WebRun does not pause, edit, or trigger a sync
Done when Any risky sync has an alert drafted and waiting for your approval.
-
3
Microsoft Teams - post the setup review
microsoft.com
WebRun opens Microsoft Teams to post the setup review. - Post the data team channel one block per new sync with a pass or fail on each checklist item
- Show the source model, the destination object, the match key, and the count of mapped fields
- Put syncs with rejected rows or no match key first, with the row counts behind each verdict
Done when The data team has this morning's new sync review in Microsoft Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it pause or edit a sync?
No. WebRun reviews the configuration and reports it. Pausing a sync, fixing a mapping, or changing a match key stays with your data team, and the Twilio alert is drafted for your approval first.
What does the checklist actually check?
Whether the sync has a match key, whether every mapped field lines up in type with its destination, which sync behaviour is set, and whether the first run rejected any rows.
Does it read the customer records being synced?
No. It reads the sync configuration and the run counts, not the rows themselves. Rejected row totals are reported as numbers, without the underlying records.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.