Automated Postmark Bounce Cleanup Reports
Every morning, WebRun signs in to Postmark, reads bounces and spam complaints logged since the last run across each server and message stream, groups the addresses by cause, raises a Trello cleanup card per stream listing the addresses to remove at source, and sends the day's totals to WhatsApp.
How do I clean up email bounces before they hurt deliverability?
WebRun signs in to Postmark every morning, reads the bounces and spam complaints logged overnight across your servers, and groups the addresses by cause and message stream. It raises a Trello cleanup card per stream and sends the day's totals to WhatsApp, so dead addresses get cleaned instead of retried forever.
- Hard bounces are grouped and listed the morning after they happen
- A bounce spike is called out against the recent daily average
- Transactional and broadcast streams are kept separate in the cleanup
Built for developers · growth teams · SaaS operators · 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
account.postmarkapp.comin a real browser with your saved login - no setup, no API keys. -
1
Postmark - read new bounces and complaints
postmarkapp.com
WebRun opens Postmark to read new bounces and complaints. - Sign in and open the activity view for each server
- List bounces and spam complaints recorded since the last run
- Group them by cause: hard bounce, soft bounce, spam complaint, or manual suppression
- Note the message stream each address belongs to and the count per cause
Done when Every new bounce and complaint is grouped by cause and message stream.
-
2
Trello - raise the cleanup cards
trello.com
WebRun opens Trello to raise the cleanup cards. - Raise a card per message stream that produced bounces overnight
- List the hard bounced and complained addresses on the card for removal at source
- Put the cause and the date against each address
- Archive a card once the addresses are cleaned from the sending system
Done when Every affected stream has a cleanup card with its addresses listed.
-
3
WhatsApp - send the daily counts
whatsapp.com
WebRun opens WhatsApp to send the daily counts. - Send today's totals by cause with the affected streams named
- Call out any spike against the recent daily average
- Stay quiet on mornings where nothing bounced
- Leave removals to a person. WebRun never deletes a suppression, a contact, or a record
Done when The team knows this morning's bounce picture in one message.
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 delete addresses or clear the suppression list?
No. WebRun reads bounce activity and writes a cleanup list. It never deletes a suppression, removes a contact, reactivates an address, or sends a message. Removal at source is done by a person.
How are bounces grouped?
By cause and by message stream: hard bounce, soft bounce, spam complaint, and manual suppression, each tied to the stream it came from, so transactional and broadcast problems never get mixed together.
Will it tell me if bounces suddenly spike?
Yes. Each morning's totals are compared with the recent daily average, and any spike is called out by cause and stream in the WhatsApp message.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.