resend-inbound

Process inbound emails via Resend webhooks and content APIs.

63|2|Updated Mar 23, 2026

Search Tags:#email #webhooks #attachments #resend #inbound #forwarding #content-retrieval

Ready to run

npx skills add https://github.com/stolinski/s-stack --skill resend-inbound-stolinski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resend-inbound
Source: https://github.com/stolinski/s-stack/tree/main/skills/resend/resend-inbound
Command: npx skills add https://github.com/stolinski/s-stack --skill resend-inbound-stolinski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of receiving and handling inbound emails by leveraging Resend domains, webhooks, and content APIs to extract body and attachments and forward messages as needed.

Core Features & Use Cases

Inbound domain configuration for Resend-managed or custom domains to receive mail.
Webhook handling for the email.received event, including metadata such as sender, subject, and attachments.
Retrieve email content and attachments on demand via the API, enabling processing, routing, and forwarding.
Forward emails with attachments to another address or system while preserving metadata.
Route messages based on recipient or other criteria to different processing paths.

Quick Start

Configure a receiving domain, subscribe to the email.received webhook, and begin processing incoming emails and their 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 emails using Resend webhooks?▼

To process inbound emails using Resend webhooks, subscribe to the email.received event to capture metadata like sender and subject, then retrieve email bodies and attachments on demand via the content API.

How do I route inbound emails to different processing paths based on recipient?▼

You can route inbound emails by applying routing decisions based on recipient or subject metadata extracted from the incoming message to forward emails to different processing paths.

What do I need to set up to receive and forward inbound emails with attachments?▼

Receiving and forwarding inbound emails with attachments requires configuring an inbound domain in Resend, subscribing to webhooks, and retrieving message content and attachments through the content API.

Can I forward inbound emails to another address while preserving metadata and attachments?▼

Yes, you can forward inbound emails with attachments to another address or system while preserving the original message metadata extracted from the received webhook event.

Does Resend inbound email handling work with custom domains?▼

Resend inbound email handling supports both Resend-managed and custom domains for receiving mail, allowing flexible domain configuration for your inbound email processing workflow.

When do I need to retrieve email content on demand versus processing it directly from the webhook?▼

You retrieve email content and attachments on demand via the API when your workflow requires processing or routing decisions, keeping webhook payloads lightweight while enabling full content access.