Automated Fivetran Connector Status Digest
Every morning, WebRun opens Fivetran, checks every connector's sync status and row counts, posts the daily digest to Slack, and sends a separate Telegram escalation for anything that's been broken more than a day.
How do I get a daily status check on all my Fivetran connectors?
WebRun checks every Fivetran connector each morning, reads its sync status and row counts, and posts a digest to Slack listing what's healthy and what's broken. A connector still broken after a day gets a separate Telegram escalation naming the error, so a stuck sync never quietly sits unfixed for a week.
- Broken connectors get caught the same morning, not at month-end reporting
- Connectors stuck more than a day get a separate escalation, not lost in the noise
- Recovered connectors clear themselves from the digest automatically
Built for data engineering teams · analytics engineers · data platform admins · BI 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
fivetran.comin a real browser with your saved login - no setup, no API keys. -
1
Fivetran - check every connector's sync status
fivetran.com
WebRun opens Fivetran to check every connector's sync status. - Open Fivetran and list every active connector
- Check each connector's last sync status and row counts
- Flag any connector that's broken or paused on an error
Done when Every active connector has a checked sync status.
-
2
Slack - post the daily digest
slack.com
WebRun posts to Slack to share the daily digest. - Post the daily connector digest to the data team channel
- List healthy connectors briefly and broken ones with the error
Done when The team has this morning's connector digest in Slack.
-
3
Telegram - escalate broken connectors
telegram.org
WebRun sends a Telegram message to escalate broken connectors. - Send a Telegram message for any connector that's been broken for more than a day
- Name the connector and the error so it can be prioritized
Done when Every connector broken more than a day has a Telegram escalation.
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 reconnect or fix a broken connector?
No. WebRun only reports the status and escalates what's stuck. Re-authorizing or fixing a connector is left to a human.
Why escalate on Telegram instead of just Slack?
A connector broken for a single day shows up in the regular Slack digest. One still broken after a day gets a separate Telegram message so it doesn't get lost in the daily noise.
What if a connector fixes itself on retry?
It reads the live sync status from Fivetran each morning, so a connector that's recovered drops out of both the digest and the escalation automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.