Automated Census Sync Reconciliation
Every hour, WebRun opens Census, checks every active sync's row counts and run status against the source warehouse model, logs the results to Google Sheets, and emails an alert naming any sync that failed or shows a row-count mismatch.
How do I catch a Census sync that's drifted from my warehouse?
WebRun checks every Census sync every hour, comparing its row counts and run status against the source warehouse model. Any mismatch or failure gets logged to Google Sheets with the sync and destination, and an email alert names the gap, so a business tool quietly drifting from your warehouse gets caught the same hour, not at next month's audit.
- Drifted syncs get caught within the hour, not at the next audit
- Every mismatch is logged with history for spotting patterns
- Business tools stay trustworthy because they match the warehouse
Built for data engineering teams · revenue operations · marketing operations · analytics engineers
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 - check sync row counts and status
- Open Census and list active syncs
- Check each sync's row counts and last-run status against the source warehouse model
- Note any sync with a row-count mismatch or a failed run
Done when Every active sync has been checked for row-count drift and status.
-
2
Google Sheets - export the discrepancy report
google.com
WebRun opens Google Sheets to export the discrepancy report. - Add a row for each sync with its row-count match and status
- Keep history so drift patterns are easy to spot
Done when This check's results are logged for every sync.
-
3
Gmail - email the alert
gmail.com
WebRun uses Gmail to email the alert. - Email an alert for any sync with a failed run or a row-count mismatch
- Name the sync, the destination, and the size of the gap
Done when An email alert has gone out for every failed or mismatched sync.
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 re-run a failed sync on its own?
No. WebRun only reports the drift or failure. Re-running a sync or fixing the underlying model is left to a human.
What counts as a row-count mismatch?
When the number of records synced to the destination doesn't match what the source warehouse model returns for the same sync, so the business tool and the warehouse are showing different numbers.
What if a sync is still running when it's checked?
A sync still in progress is noted as running rather than flagged as a mismatch, so it isn't reported as broken before it's finished.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.