All templates
For engineering teams, email infrastructure teams & SaaS platforms

Get deliverability incidents to the right engineer fast

Every hour, WebRun opens SparkPost, checks bounce rate and engagement analytics for a sudden spike or a drop in sending reputation, hands off the incident details to the deliverability owner on Slack, and sends a Telegram ping if the Slack alert hasn't been acknowledged within the hour.

  • 7-day free trial
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every hour WebRun
1 SparkPost check for a bounce or reputation spike
2 Slack hand off the incident to the owner
3 Telegram ping if it isn't acknowledged
Run a sample
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.sparkpost.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    SparkPost - check for a bounce or reputation spike
    sparkpost.com
    WebRun in SparkPost: check for a bounce or reputation spike
    WebRun opens SparkPost to check for a bounce or reputation spike.
    • Open SparkPost and check bounce rate and engagement analytics for the last hour
    • Compare against the normal range for your sending volume
    • Capture the affected sending domain or IP pool when a spike is found

    Done when The last hour's bounce and engagement numbers have been checked against normal.

  3. 2
    Slack - hand off the incident to the owner
    slack.com How to Automate Slack
    WebRun in Slack: hand off the incident to the owner
    WebRun opens Slack to hand off the incident to the owner.
    • Post the incident to the deliverability owner with the affected domain and the numbers
    • Include how far outside the normal range the spike is
    • Post nothing at all on an hour with no incident

    Done when Any hourly incident has been handed off to the owner in Slack.

  4. 3
    Telegram - ping if it isn't acknowledged
    telegram.org How to Automate Telegram
    WebRun in Telegram: ping if it isn't acknowledged
    WebRun opens Telegram to ping if it isn't acknowledged.
    • Check whether the Slack handoff was acknowledged within the hour
    • If not, send a direct Telegram ping to the same owner
    • Stop pinging once the incident is acknowledged

    Done when An unacknowledged incident has a Telegram ping sent within the hour.

How do I get SparkPost deliverability incidents to an engineer fast?

WebRun checks SparkPost every hour for a sudden bounce spike or drop in sending reputation, hands the incident off to the deliverability owner on Slack, and pings Telegram if it goes unacknowledged for an hour. Incidents reach the right person fast, with a backup channel so nothing sits unnoticed overnight.

  • A reputation spike reaches the right engineer within the hour
  • Unacknowledged incidents get a backup ping instead of sitting quiet
  • Normal sending hours stay quiet, with no noise when nothing is wrong

Built for engineering teams · email infrastructure teams · SaaS platforms · developers

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.sparkpost.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Incident handoff · Slack
OutputWhat each run produces - A Slack handoff for any bounce or reputation spike, with a Telegram ping if it goes unacknowledged.
Alert
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 it pause sending when it finds a spike?

No. WebRun only reports the incident to the deliverability owner. Pausing a sending domain or IP pool is a decision left to the person handling it.

How does it know what counts as a spike?

It compares the current hour's bounce rate and engagement against the normal range for your sending volume, not a fixed number that fits every account.

Why both Slack and Telegram?

Slack is the first handoff. Telegram is only used as a backup ping if that handoff sits unacknowledged for an hour, so a real incident doesn't get missed.

Put this on autopilot.

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