resend-inbound

Configure inbound domains, process email.received webhooks, and retrieve email content via the Resend API.

2|Updated Sep 9, 2025
One-click install
npx skills add https://github.com/yuribodo/givememoney-front --skill resend-inbound-yuribodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resend-inbound
Source: https://github.com/yuribodo/givememoney-front/tree/main/.cursor/skills/resend/resend-inbound
Command: npx skills add https://github.com/yuribodo/givememoney-front --skill resend-inbound-yuribodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates inbound email handling using Resend, including domain configuration, webhook processing, and content retrieval.

Core Features & Use Cases

  • Inbound domain setup: Configure a receiving domain or subdomain to route emails to Resend.
  • Webhook-driven processing: Subscribe to email.received to react to new messages in real time.
  • Content retrieval & forwarding: Use the Receiving and Attachments APIs to fetch body, headers, and attachments, and optionally forward emails to downstream services.

Quick Start

Follow instructions to configure a receiving domain, set up a webhook, and retrieve email content when a message arrives.

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 emails and attachments using the Resend API?

To process inbound emails with the Resend API, you configure a receiving domain, subscribe to the email.received webhook, and call the Receiving and Attachments APIs to retrieve message content and files.

How do I set up a webhook to receive inbound emails in real time?

You can receive inbound emails in real time by subscribing to the email.received webhook through the Resend API, which triggers your backend services or serverless functions whenever a new message arrives.

What's the best way to route and forward inbound emails with attachments in a serverless function?

Routing and forwarding inbound emails with attachments in serverless functions involves using the Resend API to fetch the email body, headers, and attachments, then passing that content to downstream services.

Does Resend support validating webhook signatures for inbound email processing?

Yes, validating webhook signatures is a supported part of the inbound email workflow, ensuring that the email.received events processed by your backend services are authentic and secure.

Do I need to configure a custom domain to receive inbound emails through Resend?

Yes, receiving inbound emails through Resend requires configuring a receiving domain or subdomain to route incoming messages to the service before they can trigger webhook processing.

Can I retrieve email headers and body content from inbound messages using Resend?

Yes, you can retrieve the full email body and headers from inbound messages by using the Resend Receiving API after an email.received webhook event is triggered.