Resend and Slack: Daily Bounce-and-Complaint Alert Template

A scheduled Spojit workflow that pulls recent Resend email events each morning, counts bounces and spam complaints, and posts a deliverability summary to a Slack channel so your team catches sender-reputation problems early.

What It Builds

A Schedule trigger fires every weekday morning and a Connector node on the Resend connector lists your recent emails with their delivery status. A Transform node tallies how many bounced or drew a spam complaint, and a Connector node on the Slack connector posts a short summary to your chosen channel. The result is a daily, at-a-glance deliverability check that flags reputation problems before they snowball.

The Prompt

Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow and connects the tools for you:

Build a workflow that runs every weekday at 8am Australia/Sydney time. Use the Resend connector to list emails sent in the last 24 hours, count how many bounced and how many were marked as spam complaints, then post a summary to the #deliverability Slack channel showing the total sent, the bounce count, the complaint count, and the bounce rate as a percentage.

Connectors Used

Resend - reads recent email events with the list-emails tool (use get-email in Direct mode to inspect a single message). Triggered by a Schedule trigger.
Slack - posts the summary with the send-message tool.

Customize It

Change 8am Australia/Sydney to your own cron time and IANA timezone, swap #deliverability for your team's channel, and adjust the lookback window from 24 hours to match how often you run it. To page someone when the bounce rate crosses a limit, add a line such as "and only post if the bounce rate is over 2 percent" so the alert stays quiet on healthy days.

Tips

Keep the Resend listing step in Direct mode so the count is deterministic and costs no AI credits; reserve Agent mode for cases that need judgment.
Your Slack connection needs permission to post to the target channel, and the channel must already exist.
Reference the count fields with handlebars, for example {{ summary.bounceCount }}, when you fine-tune the Slack message in the properties panel.