One-click install
npx skills add https://github.com/irchamaji/agents --skill resend-inbound-irchamaji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resend-inbound
Source: https://github.com/irchamaji/agents/tree/main/skills/resend/resend-inbound
Command: npx skills add https://github.com/irchamaji/agents --skill resend-inbound-irchamaji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you receive emails via Resend, securely verify inbound webhook events, and retrieve the actual email body and attachments that are not included in the webhook payload.

Core Features & Use Cases

  • Webhook verification for trusted events: Validates email.received webhook signatures to prevent spoofed inbound events.
  • Content retrieval after metadata-only webhooks: Fetches email HTML/text and headers using the Receiving API with the email_id from the webhook.
  • Attachment handling and forwarding: Lists attachment metadata, downloads attachment content via expiring URLs, and forwards the email with attachments to your team or system.
  • Use Case: Route incoming support vs billing emails by inspecting the recipient address in the webhook to field, then forward the enriched email content to the correct downstream handler.

Quick Start

Configure your inbound domain and webhook in Resend, then call the webhook verification endpoint to receive email.received events and use the email_id to fetch the email body and attachments.

Frequently Asked Questions about resend-inbound

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

FAQPage Schema
How do I process inbound Resend emails and download attachments from webhook events?

To process inbound Resend emails, you verify the `email.received` webhook signature, then use the `email_id` from the payload to call the Receiving and Attachments APIs for downloading the full email body and attachment content.

Why do Resend webhooks not include the email body and attachments, and how do I retrieve them?

Resend webhooks deliver metadata-only payloads for inbound emails. You retrieve the actual HTML, text, headers, and attachments by using the `email_id` from the webhook to call the Resend Receiving API and attachment expiring URLs.

How do I verify Resend webhook signatures for inbound email processing?

Verifying Resend webhook signatures requires the `RESEND_WEBHOOK_SECRET` to validate incoming `email.received` events. This prevents spoofed inbound events and ensures only trusted webhook payloads trigger downstream email retrieval.

Can I route inbound emails to different handlers based on the recipient address?

Yes, you can route inbound emails by inspecting the recipient address in the webhook `to` field. This allows you to direct support versus billing emails to separate downstream handlers after retrieving the full content.

Do I need a Resend API key to retrieve inbound email content and attachments?

Yes, retrieving inbound email content requires the `RESEND_API_KEY` to authenticate calls to the Receiving and Attachments APIs. The webhook signature verification also requires the `RESEND_WEBHOOK_SECRET` to validate events.

What is the best way to forward inbound emails with attachments to my team?

The best way to forward inbound emails with attachments is to retrieve the full email body and download attachment content via expiring URLs using the `email_id`, then forward the enriched message to your downstream system or team.