resend

Send transactional emails via the Resend API with attachments and tags.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MagicWifiMoney/openclaw-starter-kit --skill resend-magicwifimoney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resend
Source: https://github.com/MagicWifiMoney/openclaw-starter-kit/tree/main/skills-custom/resend
Command: npx skills add https://github.com/MagicWifiMoney/openclaw-starter-kit --skill resend-magicwifimoney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Send transactional emails reliably without building or maintaining complex email infrastructure, and avoid deliverability issues that cause notifications, reports, and alerts to land in spam or be delayed.

Core Features & Use Cases

  • Simple API integration — send HTML or plain-text emails, add attachments, cc/bcc, reply-to, and tags with a single REST call or the Resend Node.js SDK.
  • Deliverability-first — guidance for domain verification, DKIM/SPF/CNAME records, and best practices to minimize bounces and spam complaints.
  • Agent-driven workflows — automated daily briefings, critical alert notifications, client report delivery, welcome emails, and weekly digests for customers or internal teams.

Quick Start

Send a test email to your verified address using your RESEND_API_KEY and an HTML or text body.

Frequently Asked Questions about resend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send transactional emails from an AI agent workflow without landing in spam?

Send transactional emails reliably from AI agent workflows by integrating the Resend API, which requires a verified sending domain to ensure deliverability and prevent automated alerts from being marked as spam. It supports HTML or plain-text content via a single REST call.

Can I add attachments and tags to automated email alerts sent through the Resend API?

Yes, you can add attachments, tags, cc/bcc, and reply-to fields to automated email alerts sent through the Resend API. It supports complex email structures for client report delivery and digests using either the Resend Node.js SDK or direct REST integration.

What is the best way to handle rate limits when sending automated daily digests via transactional email?

The best way to handle rate limits when sending automated daily digests is to implement basic retry handling during transactional email delivery. This ensures that automated briefings and customer notifications are queued and resent successfully without failing.

Do I need a verified sending domain to send test transactional emails for automated notifications?

You do not need a fully verified sending domain to send test transactional emails for automated notifications because the Resend API supports a dedicated test mode. However, switching to a verified domain with proper DKIM and SPF records is required for production deliverability.

How does domain verification improve transactional email deliverability for developer-driven applications?

Domain verification improves transactional email deliverability for developer-driven applications by configuring DKIM, SPF, and CNAME records. This process authenticates your sending domain, minimizing bounces and spam complaints for automated welcome messages and alerts.

Why does my transactional email delivery fail when sending client reports with attachments via API?

Transactional email delivery fails when sending client reports with attachments if your sending domain is unverified or you exceed API rate limits without retry handling. Ensure your domain has valid DKIM and CNAME records and implement basic retry logic for rate limits.