Reconcile your Postmark delivery numbers without the spreadsheet grind
Every Monday, WebRun opens Postmark, pulls bounce and delivery stats broken down by message stream, archives the report to Google Drive, and sends a Twilio text to the on-call engineer only if a stream's bounce rate has crossed a critical level.
- 7-day free trial
- Under $0.01 per run
- Cancel anytime
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 - pull bounce and delivery stats
WebRun opens Postmark to pull bounce and delivery stats. - Open Postmark and pull the week's delivery and bounce stats for each message stream
- Separate transactional from broadcast stream results
- Flag any stream whose bounce rate crossed the critical level you set
Done when Every message stream has a current week's delivery and bounce figure.
-
2
Google Drive - archive the reconciled report
WebRun opens Google Drive to archive the reconciled report. - Archive this week's reconciled report to the shared Drive folder
- Keep prior weeks' reports in place so trends are easy to compare
- Name each file with the week's date for quick lookup
Done when This week's reconciled report is archived in Drive.
-
3
Twilio - text on-call for a critical bounce rate
WebRun opens Twilio to text on-call for a critical bounce rate. - If any stream's bounce rate crossed the critical level, text the on-call engineer
- Name the stream and the current bounce rate in the text
- Send no text at all on a normal week
Done when The on-call engineer is texted only when a stream is at a critical bounce rate.
How do I reconcile Postmark delivery and bounce stats every week?
WebRun pulls your Postmark delivery and bounce stats by message stream every Monday, archives the reconciled report to Google Drive, and texts the on-call engineer through Twilio only if a stream's bounce rate crosses a critical level. The team gets a clean weekly record and a fast alert path when something actually needs attention.
- A critical bounce rate reaches the on-call engineer by text, not just a dashboard no one is watching
- Every week's delivery numbers are archived by message stream automatically
- Transactional and broadcast performance stay reconciled separately
Built for developers · engineering teams · SaaS platforms · email infrastructure teams
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 I get texted every week?
No. The Twilio text only goes out when a message stream's bounce rate crosses the critical level you set. Most weeks produce only the archived report, no text.
Does it separate transactional from marketing email?
Yes. It reports by Postmark message stream, so transactional and broadcast sends are reconciled separately rather than blended into one number.
Can it pause sending if a stream looks bad?
No. WebRun only reports and alerts. Pausing a stream or investigating the cause is left to the engineer it texts.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.