Automated Matillion Job Run Digest
Every morning, WebRun opens Matillion, checks overnight job runs against their usual status and row counts, posts a Slack digest of what's healthy and what's broken, and sends a Telegram escalation for any job that's failed more than once this week.
How do I get a daily digest of Matillion ETL job runs?
WebRun checks Matillion job runs every morning, reading each job's status and row counts against its usual pattern. It posts a Slack digest of what's healthy and what's broken, and a job failing more than once in the same week gets a separate Telegram escalation naming the recurring error, so a broken pipeline doesn't stay buried in routine noise.
- Failed jobs get caught the same morning instead of at the next run
- Repeatedly failing jobs get a separate escalation, not lost in the noise
- The team starts the day with one Slack summary instead of checking each job
Built for data engineering teams · ETL developers · 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
matillion.comin a real browser with your saved login - no setup, no API keys. -
1
Matillion - check job run status
- Open Matillion and list overnight job runs
- Check each job's status and row counts against its usual pattern
- Note any job that's failed more than once this week
Done when Every overnight job run has a checked status.
-
2
Slack - post the digest
slack.com
WebRun posts to Slack to share the digest. - Post the digest to the data engineering channel with each job's status
- List healthy jobs briefly and failed ones with the error
Done when The team has this morning's job digest in Slack.
-
3
Telegram - escalate a repeat failure
telegram.org
WebRun sends a Telegram message to escalate a repeat failure. - Send a Telegram message for any job that's failed more than once this week
- Name the job and the recurring error
Done when Every repeatedly failing job 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 re-run a failed job on its own?
No. WebRun only reports the failure and escalates what's persistent. Re-running a job or fixing the underlying transformation is left to a human.
Why does a repeat failure get a separate Telegram message?
A single failure shows up in the regular Slack digest. A job failing more than once in the same week means it's a pattern worth a dedicated Telegram message so it doesn't get missed.
What if a job recovers on its own next run?
It checks the latest run status each morning, so a job that's back to succeeding 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.