Daily
Get yesterday's Postmark stats each morning
One email tells you how many messages went out, the bounce rate and any spam complaints.
- Runs
- Daily
- Apps
- Postmark
- AI
- Not needed
- Access
- Server token
Send this to your assistant
Create a ClickRuntime automation: every day at 8am, email me yesterday's Postmark sent count, bounce rate and number of spam complaints for my Transactional server.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A founder or developer who runs transactional email through Postmark rarely checks the stats page until something is wrong. By the time a customer says a receipt never arrived, the bounce rate may have been climbing for a week, or a bad import may have produced a handful of spam complaints that are quietly lowering your sender reputation.
Each morning, ClickRuntime pulls Postmark's outbound overview for the previous day and emails you the numbers: messages sent, bounces, bounce rate, spam complaints and spam complaint rate. It reads a fixed full day, so the figures are comparable from one email to the next and you can scan them in a few seconds.
It suits small teams without a dedicated email person, and anyone who wants a record of sending volume that does not depend on remembering to log in.
What you get out of it
Rate changes show up the next morning
A bounce rate that moves from 1 percent to 4 percent is easy to miss in a dashboard you rarely open. In a daily email it stands out within a day, while you can still trace it to a specific import or release.
Volume doubles as a business signal
Sends per day track signups, orders and password resets. A sudden drop in messages can mean a broken checkout or a failed deploy, so the stats email sometimes reveals a problem unrelated to email entirely.
You build a history without effort
Every email is a dated snapshot of how sending went. When you need to explain a deliverability dip to a client or to Postmark support, you can scroll back instead of reconstructing the numbers from memory.
Complaints are caught while they are few
A spam complaint rate is a tiny percentage, so single digits of complaints matter. Seeing the count daily lets you pause a campaign or fix a sign-up form before mailbox providers start filtering you.
No login, no habit required
The numbers arrive where you already read mail. That removes the discipline problem, because a check that depends on remembering to look is the one that gets skipped during a busy launch week.
How it works
What happens, step by step
Every morning, ClickRuntime pulls yesterday's sending summary from Postmark.
It reads how many messages went out, the bounce rate and the number of spam complaints.
You get one email with those three figures and the sent count in the subject line.
Before it runs live
- Connect Postmark
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Postmark steps into one automation
Under the hood
The code that runs this automation
from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify
@on_trigger
def run(event):
day = str(date.today() - timedelta(days=1))
resp = http.get("https://api.postmarkapp.com/stats/outbound", params={"fromdate": day, "todate": day},
headers={"Accept": "application/json",
"X-Postmark-Server-Token": credentials.secret("POSTMARK_SERVER_TOKEN")})
resp.raise_for_status()
s = resp.json()
notify.email_me(f"Postmark {day}: {s['Sent']} sent",
f"Sent: {s['Sent']}\nBounce rate: {s['BounceRate']}%\nSpam complaints: {s['SpamComplaints']}")
return {"sent": s["Sent"], "bounce_rate": s["BounceRate"]}FAQ
Common questions
Which day does the report cover?
What does Postmark count as a bounce versus a spam complaint?
Can the report cover just one message stream?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Reactivate addresses that bounced temporarily
People whose mailbox had a temporary problem get your emails again, and you see who was reactivated.
See how it worksGet bounces and spam complaints in Slack
Support sees each bounce or complaint with the address, type and subject, once.
See how it worksKnow the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksKeep exploring
Set up “Get yesterday's Postmark stats each morning” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
