resend-inbound

Process verified Resend inbound email webhooks into messages with attachments.

1|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/cgRGM/rivercitymd --skill resend-inbound-cgrgm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resend-inbound
Source: https://github.com/cgRGM/rivercitymd/tree/main/.agents/skills/resend/resend-inbound
Command: npx skills add https://github.com/cgRGM/rivercitymd --skill resend-inbound-cgrgm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you receive, verify, and process inbound emails sent through Resend without missing message content, attachments, or routing details.

Core Features & Use Cases

  • Inbound domain setup: Configure either a Resend-managed receiving address or a custom domain with the correct MX routing.
  • Webhook verification: Validate email.received events using Resend signature verification before trusting the payload.
  • Email content retrieval: Fetch the full message body, headers, and attachments through the receiving APIs after a webhook arrives.
  • Forwarding and routing: Route messages by recipient and forward emails with attachments to internal teams or downstream systems.
  • Use Case: A support inbox can receive customer emails, verify each webhook, download attachments, and automatically forward the message to the right department.

Quick Start

Use the resend-inbound skill to help me set up inbound email handling for a Resend domain, verify webhook events, and retrieve the full message content 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 email webhooks and retrieve full message content?

To process inbound Resend email webhooks, you verify the email.received event signature and then use receiving APIs to retrieve the full message body, headers, and attachments after the metadata-only webhook is delivered.

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

Verifying Resend webhook signatures involves validating the email.received event payload using Resend signature verification before trusting the inbound email content, ensuring the webhook request is authentic and unmodified.

Do I need MX records to set up a custom domain for receiving inbound email with Resend?

Yes, setting up a custom domain for receiving inbound email with Resend requires configuring the correct MX routing records to direct messages to your receiving domain, or you can use a Resend-managed receiving address.

Can I route inbound emails to different recipients and forward attachments automatically?

Yes, you can route inbound emails by recipient and automatically forward messages with attachments to internal teams or downstream systems after downloading the files through the receiving APIs.

What's the best way to download email attachments from Resend inbound webhooks?

The best way to download email attachments from Resend inbound webhooks is to fetch the files through the receiving APIs after the webhook arrives, because the webhook itself only delivers message metadata and not the actual file content.

Why does my Resend inbound webhook only contain email metadata and not the message body?

Resend inbound webhooks only contain email metadata by design, requiring you to call the receiving APIs to retrieve the full message body and attachments after the webhook event is verified and delivered.