Automated Email on Acid Pre-Send Failure Alerts
Every hour, WebRun checks Email on Acid for pre-send test results on campaigns scheduled to go out soon, posts a Slack alert the moment a client rendering test or spam test comes back failing, and escalates to Telegram if the send time is within two hours and the issue still has not been fixed.
How do I catch a failing Email on Acid test before a campaign sends?
WebRun checks Email on Acid every hour for pre-send test results on campaigns scheduled to go out soon, posts a Slack alert the moment a client rendering or spam test fails, and escalates to Telegram if the issue is still unresolved within two hours of send. Broken campaigns get caught before they reach an inbox, not after.
- Rendering and spam failures get caught before a campaign goes out
- Urgent failures close to send time get escalated automatically
- No campaign ships on a failing test unnoticed
Built for email marketing teams · email developers · marketing operations · agencies sending client campaigns
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.emailonacid.comin a real browser with your saved login - no setup, no API keys. -
1
Email on Acid - check pre-send test results
emailonacid.com
WebRun opens Email on Acid to check pre-send test results. - Open Email on Acid and review tests for campaigns scheduled to send soon
- Read the client rendering results and the spam test score
- Note any client or test that came back failing
Done when Every upcoming campaign's test results are read and any failures are noted.
-
2
Slack - post the failure alert
slack.com
WebRun opens Slack to post the failure alert. - Post a Slack alert the moment a test comes back failing
- Name the campaign, the failing client or test, and its scheduled send time
- Post nothing for campaigns that pass cleanly
Done when The team has a Slack alert for every failing pre-send test.
-
3
Telegram - escalate close to send time
telegram.org
WebRun opens Telegram to escalate close to send time. - Check whether a failing campaign is still unresolved within two hours of its send time
- Escalate to the marketing Telegram channel if so
- Include the send time so the team knows how urgent it is
Done when An unresolved failure within two hours of send has been escalated to Telegram.
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
Does it stop a campaign from sending?
No. WebRun only reports test failures and escalates urgent ones. Pausing or fixing the campaign stays with your team in Email on Acid and your sending platform.
What counts as urgent enough for Telegram?
A test that is still failing within two hours of its scheduled send. Anything caught earlier only needs the Slack alert.
Does it retest automatically after a fix?
It reads Email on Acid's latest results each hour, so a fixed and rerun test shows as passing on the very next check.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.