Reconcile Hightouch syncs before they drift
Every hour, WebRun opens Hightouch, checks every active sync's row counts and run status against the source model, exports a discrepancy report to Drive, and posts a Slack alert naming any sync that failed or shows a mismatch.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch a Hightouch sync that's drifted from my warehouse?
WebRun checks every Hightouch sync every hour, comparing its row counts and run status against the source model. Any mismatch or failure gets exported to a discrepancy report in Google Drive and posted as a Slack alert naming the sync and destination, so a business tool quietly drifting from your warehouse gets caught the same hour.
- Drifted syncs get caught within the hour, not at the next audit
- Every mismatch is exported with a running 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.hightouch.comin a real browser with your saved login - no setup, no API keys. -
1
Hightouch - check sync row counts and status
hightouch.com
WebRun opens Hightouch to check sync row counts and status. - Open Hightouch and list active syncs
- Check each sync's row counts and last-run status against the source 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 Drive - export the discrepancy report
drive.google.com How to Automate Google Drive
WebRun opens Google Drive to export the discrepancy report. - Export the discrepancy report with the sync, destination, and gap size to the shared Drive folder
- Keep a running file so drift patterns are easy to spot
Done when This check's discrepancy report is saved to Drive.
-
3
Slack - post an alert for failures
slack.com How to Automate Slack
WebRun posts to Slack to alert on failures. - Post an alert to the data team channel for any sync that failed or shows a mismatch
- Name the sync, the destination, and the size of the gap
Done when The team has a Slack alert 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 a destination doesn't match what the source model returns for the same sync, so a 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.