Daily Amazon SES bounce, complaint, and blacklist digest posted to Slack

PromptCreate

Every weekday at 9am, pull an Amazon SES deliverability health snapshot and post a short readable summary to a Slack channel.

For the last 24 hours, use Amazon SES List Suppressed Destinations to fetch the email addresses that were added to my suppression list because of bounces and complaints. Group them by reason so I can see the top bounce/complaint categories at a glance.

Then use Amazon SES List Email Identities to enumerate my verified sending domains, and for each verified domain call Amazon SES Get Domain Statistics Report to pull inbox placement, engagement, spam-complaint rate, and bounce rate. If Get Domain Statistics Report returns empty for a domain, note in the digest that the SES deliverability dashboard is not enabled for it, so I know why the numbers are missing.

If I have any dedicated IP pools (check with Amazon SES List Dedicated IP Pools), call Amazon SES Get Blacklist Reports for those pools and surface any active blacklist hits. If I only send from shared IPs, skip this section entirely.

Write a short, readable summary that includes: how many new suppressions were added in the last 24 hours, the top bounce reasons, per-domain complaint and bounce rate with a plain-English note on whether any domain is trending toward Amazon's warning thresholds (bounce rate above 5% or complaint rate above 0.1%), and any dedicated-IP blacklist hits. Use Amazon's own guardrails as the reference: bounce rate above 5% triggers a review and above 10% causes SES to pause sending; complaint rate above 0.1% triggers review and above 0.5% causes pause.

Post the summary to my ops Slack channel using Slack Bot Send a Message. Format it with Slack mrkdwn so headings and rates are readable at a glance. If any threshold is breached or a blacklist hit is found, prepend the message with @channel and include a one-line "here's what to check next" call to action naming the specific domain, rate, or IP that tripped the alert. If everything is healthy, keep the message short and skip the tag.

What does this prompt do?

Every weekday at 9am, checks the past 24 hours of Amazon SES bounces and complaints and rolls them into a short Slack summary.
Names the top reasons your emails are failing (mailbox not found, blocked, spam-flagged, and more) so you know what to fix first.
Watches your bounce and complaint rates against Amazon's own warning thresholds and flags it in Slack if you're getting close.
If you use a dedicated IP pool, checks those IPs against public blacklists and tags the channel when a threshold is breached or an IP is flagged.

What do I need to use this?

An Amazon SES account with the deliverability dashboard turned on. That is what powers the per-domain inbox placement and engagement numbers in the digest.
A Slack workspace and a channel where you want the digest posted.
Optional: a dedicated IP pool. Without one, the blacklist section is skipped and the rest of the digest runs normally.

How can I customize it?

Change the schedule (mornings only, midday, once a week, or every day including weekends).
Send the digest to a different Slack channel, a private channel, or a direct message.
Adjust the warning thresholds. Amazon's defaults are a bounce rate above 5% and a complaint rate above 0.1%.

FAQs

What exactly does the digest cover?

New bounces and complaints from the last 24 hours, per-domain inbox placement and engagement, whether your spam-complaint or bounce rate is trending toward Amazon's warning thresholds, and any blacklist hits on dedicated IPs.

Do I need to turn on the Amazon SES deliverability dashboard?

Yes, if you want per-domain inbox placement and engagement numbers. Without it the workflow still runs, but that section of the digest will be empty and will note that the dashboard is off.

Does this work if I don't use dedicated IPs?

Yes. If you send from shared Amazon IPs the blacklist section is skipped and the rest of the digest (bounces, complaints, per-domain rates) runs normally.

What thresholds trigger the @channel alert?

Amazon reviews accounts with a bounce rate above 5% and pauses sending above 10%. Complaint rates above 0.1% trigger review, and above 0.5% pause sending. The digest tags the channel if you are trending toward either.

Will it post on weekends?

No, weekdays only by default. You can change the schedule to daily, weekly, or any cron time when you customize the workflow.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

+1

Agentic Task

Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Agentic Task

Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agentic Task

Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Agentic Task

Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Agentic Task

Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.