All templates
For Data engineering teams, Analytics engineers & Data platform teams

Catch data anomalies Metaplane flags before anyone else does

Every few minutes, WebRun opens Metaplane, checks for any new volume, freshness, or schema anomaly on your monitored tables, posts the alert to Slack naming the table and exactly what changed, and pings the on-call data engineer on Telegram, so a silent pipeline break gets caught before it reaches a dashboard or a report.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every few minutes, around the clock WebRun
1 Metaplane check for new anomalies
2 Slack post the anomaly
3 Telegram ping the on-call engineer
Run a sample
In short

How do I get alerted immediately to a data anomaly Metaplane detects?

WebRun checks Metaplane every few minutes for new volume, freshness, or schema anomalies on your monitored tables. The moment one appears, it posts the table and what changed to Slack, and pings the on-call data engineer on Telegram, so a silent pipeline break gets caught before it quietly shows up as wrong numbers on a dashboard.

  • Data anomalies get caught within minutes instead of at the next dashboard review
  • The on-call engineer is pinged on Telegram so nothing waits on someone opening Slack
  • Every anomaly comes with the specific table and metric, not a vague warning

Built for Data engineering teams · Analytics engineers · Data platform teams · On-call engineers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.metaplane.dev in a real browser with your saved login - no setup, no API keys.

  2. 1
    Metaplane - check for new anomalies
    metaplane.dev
    WebRun in Metaplane: check for new anomalies
    WebRun opens Metaplane to check for new anomalies.
    • Open Metaplane and check monitored tables for new anomalies
    • Read whether each is a volume, freshness, or schema anomaly
    • Capture the table, the metric, and how far it moved from normal

    Done when Every new anomaly has been captured with its detail.

  3. 2
    Slack - post the anomaly
    slack.com How to Automate Slack
    WebRun in Slack: post the anomaly
    WebRun opens Slack to post the anomaly.
    • Post the table name, anomaly type, and the detail to the data team channel
    • Group anomalies from the same table into one message
    • Link to the anomaly in Metaplane if possible

    Done when The data team channel has a post for every new anomaly.

  4. 3
    Telegram - ping the on-call engineer
    telegram.org How to Automate Telegram
    WebRun in Telegram: ping the on-call engineer
    WebRun opens Telegram to ping the on-call engineer.
    • Message the on-call data engineer with the affected tables
    • Send only while there is at least one unresolved anomaly
    • Keep the message short and specific

    Done when The on-call engineer has been pinged about today's anomalies.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.metaplane.dev
ScheduleRuns automatically on this cadence
Every few minutes, around the clock
DeliveryHow each run's result reaches you
Anomaly alert · Slack
OutputWhat each run produces - A post naming the table, anomaly type, and detail, sent to Slack and Telegram.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does WebRun set up the anomaly detection itself?

No. It reads anomalies Metaplane has already detected using the monitors you configured. It does not create or tune monitors.

Does it fix the pipeline that caused the anomaly?

No. It only reports what changed and where. Investigating and fixing the underlying pipeline stays with your data engineer.

Why does it post to both Slack and Telegram?

Slack keeps a shared record for the whole data team, while Telegram makes sure the on-call engineer sees it right away, even away from a desk.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.