resend-inbound

Automates Resend email.received webhooks and retrieves message content and attachments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates inbound email processing by handling Resend's email.received webhooks and retrieving the full message content and attachments for downstream workflows.

Core Features & Use Cases

  • Webhook-driven inbound processing: Receive metadata from email.received webhooks and fetch the message body and attachments when needed.
  • Domain and routing setup: Configure receiving domains (Resend-managed or custom) and route or forward emails to appropriate handlers.
  • Content retrieval and forwarding: Retrieve email content via the Receiving API and attachments via the Attachments API, then forward or process the data in your application.

Quick Start

  1. Configure your receiving domain (Resend-managed or custom) and subscribe to the email.received webhook.
  2. Verify webhook signatures and start processing inbound events.
  3. Use the Receiving API to fetch body/html/text and the Attachments API to fetch attachments, then forward or route as needed.

Frequently Asked Questions about resend-inbound

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

FAQPage Schema
How do I automate inbound email processing with webhooks?

You can automate inbound email processing by subscribing to the email.received webhook to capture metadata, then using the Receiving and Attachments APIs to retrieve full message content and route it downstream.

How do I retrieve email attachments using the Resend API?

You retrieve email attachments by using the Resend Attachments API to fetch files associated with an inbound message after the initial email.received webhook delivers the event metadata to your handler.

Do I need to verify webhook signatures for Resend inbound emails?

Yes, secure webhook verification is required to validate the email.received events, ensuring that the inbound email metadata and subsequent content retrieval requests are authentic and safely processed.

What is the best way to configure a receiving domain for inbound email automation?

Configuring a receiving domain for inbound email involves setting up either a Resend-managed or custom domain, then subscribing to the email.received webhook to start routing events to your application.

Can I forward inbound email content in a serverless environment?

Yes, you can forward inbound email content in serverless or hosted environments by retrieving the body and attachments via the API and routing the assembled data to your downstream application handlers.