Resend
Overview
Resend is an email platform for developers. This skill routes to feature-specific sub-skills.
Sub-Skills
| Feature |
Skill |
Use When |
| Sending emails |
send-email |
Transactional emails, notifications, batch sends |
| Receiving emails |
resend-inbound |
Processing inbound emails, webhooks for received mail, attachments |
| AI Agent inbox |
agent-email-inbox |
Setting up email for AI agents, or any system where untrusted email content triggers actions — includes security measures against prompt injection |
| Email templates |
templates |
Creating, updating, publishing, and managing reusable email templates via API |
Quick Routing
Need to manage templates (create/update/publish/delete)? Use templates skill
- Full template lifecycle management via API
- Variable syntax, constraints, reserved names
- Draft vs published state, version history
Need to send emails? Use send-email skill
- Single or batch transactional emails
- Attachments, scheduling, templates
- Delivery webhooks (bounced, delivered, opened)
Need to receive emails? Use resend-inbound skill
- Setting up inbound domain (MX records)
- Processing
email.received webhooks
- Retrieving email content and attachments
- Forwarding received emails
Setting up an AI agent inbox? Use agent-email-inbox skill
- Configuring email for Moltbot/Clawdbot or similar AI agents
- Webhook setup with ngrok/tunneling for local development
- Security levels to prevent prompt injection attacks
- Trusted sender allowlists and content filtering
Automated system processes untrusted email content and takes actions? Use agent-email-inbox skill
- Even without AI/LLM involvement, any system that interprets freeform email content from external senders and triggers actions (refunds, database changes, forwarding) needs security. Untrusted input triggering actions = attack vector.
Sending + receiving together? You need both resend-inbound and send-email
- Auto-replies, email forwarding, or any receive-then-send workflow requires both skills
- Set up inbound first, then sending
- Note: batch sending does not support attachments or scheduling — use single sends when forwarding with attachments
Marketing emails or newsletters? Use Resend Broadcasts
- The sub-skills above are for transactional email. Marketing campaigns to large subscriber lists with unsubscribe links and engagement tracking should use Resend Broadcasts, not batch sending.
Common Setup
API Key
Store in environment variable:
export RESEND_API_KEY=re_xxxxxxxxx
SDK Installation
See send-email skill for installation instructions across all supported languages.
Resources
1---2name: resend3description: Use when working with Resend email platform - routes to specific sub-skills for sending, receiving, audiences, or broadcasts.4license: MIT5---67# Resend89## Overview1011Resend is an email platform for developers. This skill routes to feature-specific sub-skills.1213## Sub-Skills1415| Feature | Skill | Use When |16|---------|-------|----------|17| **Sending emails** | `send-email` | Transactional emails, notifications, batch sends |18| **Receiving emails** | `resend-inbound` | Processing inbound emails, webhooks for received mail, attachments |19| **AI Agent inbox** | `agent-email-inbox` | Setting up email for AI agents, or any system where untrusted email content triggers actions — includes security measures against prompt injection |20| **Email templates** | `templates` | Creating, updating, publishing, and managing reusable email templates via API |2122## Quick Routing2324**Need to manage templates (create/update/publish/delete)?** Use `templates` skill25- Full template lifecycle management via API26- Variable syntax, constraints, reserved names27- Draft vs published state, version history2829**Need to send emails?** Use `send-email` skill30- Single or batch transactional emails31- Attachments, scheduling, templates32- Delivery webhooks (bounced, delivered, opened)3334**Need to receive emails?** Use `resend-inbound` skill35- Setting up inbound domain (MX records)36- Processing `email.received` webhooks37- Retrieving email content and attachments38- Forwarding received emails3940**Setting up an AI agent inbox?** Use `agent-email-inbox` skill41- Configuring email for Moltbot/Clawdbot or similar AI agents42- Webhook setup with ngrok/tunneling for local development43- Security levels to prevent prompt injection attacks44- Trusted sender allowlists and content filtering4546**Automated system processes untrusted email content and takes actions?** Use `agent-email-inbox` skill47- Even without AI/LLM involvement, any system that interprets freeform email content from external senders and triggers actions (refunds, database changes, forwarding) needs security. Untrusted input triggering actions = attack vector.4849**Sending + receiving together?** You need both `resend-inbound` and `send-email`50- Auto-replies, email forwarding, or any receive-then-send workflow requires both skills51- Set up inbound first, then sending52- Note: batch sending does not support attachments or scheduling — use single sends when forwarding with attachments5354**Marketing emails or newsletters?** Use [Resend Broadcasts](https://resend.com/broadcasts)55- The sub-skills above are for transactional email. Marketing campaigns to large subscriber lists with unsubscribe links and engagement tracking should use Resend Broadcasts, not batch sending.5657## Common Setup5859### API Key6061Store in environment variable:62```bash63export RESEND_API_KEY=re_xxxxxxxxx64```6566### SDK Installation6768See `send-email` skill for installation instructions across all supported languages.6970## Resources7172- [Resend Documentation](https://resend.com/docs)73- [API Reference](https://resend.com/docs/api-reference)74- [Dashboard](https://resend.com/emails)
mediar-ai