Catch Sailthru send failures the moment they happen
Every hour, WebRun opens Sailthru, checks triggered and lifecycle campaigns for send errors or failed personalization data, posts a Telegram alert the moment a campaign shows a failure, and texts the on-call engineer through Twilio when the failure affects a currently live, actively sending campaign.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch a Sailthru campaign send failure quickly?
Every hour, WebRun checks Sailthru's triggered and lifecycle campaigns for send errors or failed personalization data, posts a Telegram alert the moment one appears, and texts the on-call engineer through Twilio when the failure affects a currently live campaign. Broken sends get caught within the hour instead of after subscribers notice.
- Send failures get caught within the hour they happen
- Only live campaign failures wake the on-call engineer
- Personalization errors get caught before subscribers see broken content
Built for media and retail marketing teams · email engineering teams · marketing operations · enterprise email marketers
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
www.sailthru.comin a real browser with your saved login - no setup, no API keys. -
1
Sailthru - check for send errors
sailthru.com
WebRun opens Sailthru to check for send errors. - Open Sailthru and review triggered and lifecycle campaign activity
- Check for send errors or failed personalization data
- Note which campaigns are affected and whether they are currently live
Done when Every campaign with a send error is listed with its status.
-
2
Telegram - post the failure alert
telegram.org How to Automate Telegram
WebRun opens Telegram to post the failure alert. - Post a Telegram alert the moment a campaign shows a send error
- Name the campaign and the type of error
- Post nothing when every campaign is sending cleanly
Done when The team has a Telegram alert for every campaign send error.
-
3
Twilio - text the on-call engineer
twilio.com How to Automate Twilio
WebRun opens Twilio to text the on-call engineer. - Text the on-call engineer only when the failure affects a currently live, actively sending campaign
- Include the campaign name and error type
- Skip the text for errors on paused or scheduled campaigns
Done when The on-call engineer is texted only for a live campaign failure.
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 fix the send error?
No. WebRun only detects and reports the failure. Diagnosing and fixing the underlying issue stays with your engineering team.
Why does a live campaign get a text but a scheduled one does not?
Because a failure on a campaign that is actively sending right now needs faster attention than one that has not gone out yet.
How is a personalization data failure different from a send error?
Both are treated as failures. A personalization failure means the content could not be built correctly, which is just as important to catch as a delivery error.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.