Verified:GitHub

resend

Send and receive transactional emails via Resend with webhook verification.

Updated Apr 24, 2026

Search Tags:#webhooks #idempotency #transactional emails #sdk integration #template variables #email receiving #delivery events

Ready to run

npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill resend-otto-poblysh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resend
Source: https://github.com/otto-poblysh/pedagemy-early-access/tree/main/.agents/skills/resend
Command: npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill resend-otto-poblysh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you send and receive transactional emails correctly with Resend while avoiding production issues that commonly cause duplicate sends, broken webhooks, or missing email bodies.

Core Features & Use Cases

Send transactional emails (single or batch): Send one-off messages or batches with the right constraints (e.g., no attachments/scheduling in batch).
Webhook-based receiving: Receive inbound email events securely and fetch the actual email body and attachments via the receiving APIs.
Production-safe reliability: Apply critical patterns like idempotency keys, webhook signature verification, and correct SDK error handling.

Quick Start

Use the resend skill to send a transactional email using your RESEND_API_KEY and include an idempotency key to prevent duplicates.

Frequently Asked Questions about resend

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

FAQPage Schema

How do I prevent duplicate transactional emails when sending with the Resend SDK?▼

To prevent duplicate transactional emails, use an idempotency key when calling the Resend SDK. This ensures that if a request is retried or sent multiple times, the server recognizes the duplicate request and does not send the same email twice.

What's the best way to verify Resend webhook signatures for inbound email events?▼

The best way to verify Resend webhook signatures is by using your RESEND_WEBHOOK_SECRET to validate the incoming payload. This confirms the webhook event was sent by Resend and prevents unauthorized or tampered delivery events from being processed.

Can I send batch transactional emails with template variables using Resend?▼

Yes, you can send batch transactional emails with template variables using Resend. However, batch sends have specific constraints, such as not supporting attachments or scheduling, so you must structure your payload to accommodate these limitations.

How do I retrieve the actual email body and attachments from Resend receiving webhooks?▼

To retrieve the actual email body and attachments from Resend receiving webhooks, you must fetch them separately using the receiving APIs. The webhook itself only provides metadata, requiring a subsequent API call to get the full content.

Do I need an API key to manage Resend domains and handle delivery events?▼

Yes, you need a RESEND_API_KEY to manage domains, handle delivery events, and authenticate any operational tasks with Resend. Optionally, a RESEND_WEBHOOK_SECRET is required if you are verifying signatures for inbound webhook events.