Automated Litmus Pre-Send Email QA Checks
Every morning, WebRun opens Litmus, reviews the email client previews and spam tests for campaigns queued to send, logs any rendering or spam-score problems to Google Sheets, and posts a pass or fail digest to Notion before anyone hits send.
How do I catch email rendering and spam issues before a campaign sends?
WebRun reviews your Litmus preview and spam-test results every morning for campaigns queued to send, logs any client-rendering or spam-score problems to Google Sheets, and posts a pass or fail digest to Notion. The team sees exactly which campaigns are clear to send and which need a fix, before anything goes out broken.
- Broken campaigns get caught before they reach a single inbox
- The team sees a pass or fail digest every morning instead of after complaints roll in
- Rendering and spam-score issues are logged so repeat problems are easy to spot
Built for email marketers · marketing ops · ESP admins · in-house creative 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
litmus.comin a real browser with your saved login - no setup, no API keys. -
1
Litmus - check previews and spam tests
litmus.com
WebRun opens Litmus to check previews and spam tests. - Open Litmus and list campaigns queued to send today
- Review the email client previews for broken layouts or clipped images
- Check the spam test score for each campaign
Done when Every queued campaign has a preview check and a spam score.
-
2
Google Sheets - log issues found
google.com
WebRun opens Google Sheets to log issues found. - Log each campaign with its spam score and any client-rendering issues found
- Flag campaigns with a failing score or a broken preview
- Keep a running history so repeat issues are easy to spot
Done when Every checked campaign has a row with its result.
-
3
Notion - post the pass or fail digest
notion.so
WebRun opens Notion to post the pass or fail digest. - Post today's pass or fail digest to the team's QA page
- List which campaigns are clear to send and which need a fix
- Leave the fix to the sender. WebRun only flags issues, it never edits or sends a campaign
Done when The team has today's QA digest in Notion before send time.
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 stop a broken campaign from sending?
No. WebRun only flags rendering and spam-score problems in the digest. It never edits, pauses, or sends a campaign. A person still decides what to do with a flagged one.
Which email clients does it check?
Whatever previews and spam tests you already run in Litmus for that campaign. WebRun reads the existing results rather than running new tests of its own.
What if a campaign was already fixed after the last check?
It reads Litmus fresh each morning, so a resolved issue simply drops off the next digest.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.