Resend and Slack: Failed-Email Send Alert Template
A scheduled Spojit workflow that reviews recent Resend emails, flags any that failed or were not delivered, and posts a heads-up to a Slack channel so your team can re-send important customer messages fast.
What It Builds
A Schedule trigger fires on a Unix cron interval (for example every morning on weekdays) and a Connector node on the Resend connector pulls your recent emails with list-emails. A Condition node keeps only the ones whose status shows a failure or non-delivery, and a Connector node on the Slack connector posts a summary to a channel with send-message. The result: your team sees stuck customer emails in Slack instead of discovering them later.
The Prompt
Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow, connecting the tools for you:
Build a workflow that runs every weekday at 9am, lists my recent Resend emails, keeps only the ones that failed or were not delivered, and posts a message to the #email-alerts Slack channel listing each failed email's recipient, subject, and status so my team can re-send them.
Connectors Used
- Schedule trigger - runs the workflow on a 5-field Unix cron schedule and timezone you choose (for example
0 9 * * 1-5inAustralia/Sydney). - Resend - lists your recent emails with
list-emailsand can pull full detail on any one withget-email. - Slack - posts the alert to a channel with
send-message.
Customize It
Change the cron time and frequency in the prompt (for example hourly with 0 * * * *), swap #email-alerts for your own channel, and adjust which fields the Slack message includes. You can also tighten what counts as a problem (only hard failures versus anything not yet delivered) by editing that phrase in the prompt, then fine-tune the Condition node and the message body in the properties panel after Miraxa scaffolds it.
Tips
- Use the Resend and Slack nodes in Direct mode here: the calls are predictable single tools, so you avoid AI credit cost. Save Agent mode for when you want the workflow to summarize or prioritize failures in its own words.
- A Schedule trigger can hold multiple schedules, so you can add a second, more frequent run during busy campaign sends without building a separate workflow.
- Keep the lookback window short and the page size sensible in the
list-emailsstep so each run stays fast and you alert only on recent activity.
Related
- How to Build Email Notifications with Resend walks through the Resend connector step by step.
- How to Set Up Multi-Channel Notifications (Email + Slack) shows how to fan the same alert out to more places.
- How to Set Up Slack Alerts for Workflow Failures is the sibling pattern for failed workflow runs.