resend-inbound

Validate Resend webhooks and retrieve email content and attachments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently handle inbound emails by validating Resend webhooks and retrieving full message content and attachments, so you can build reliable email-driven workflows without implementing mailbox parsing yourself.

Core Features & Use Cases

  • Webhook verification and secure inbound processing for email.received events.
  • Retrieve email bodies and attachments on demand, then route or forward as needed.
  • Use cases include automated ticket creation, support routing, or archiving email content for later processing.

Quick Start

Configure a webhook endpoint, verify inbound events, and fetch email content and attachments on demand.

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 from a webhook securely?

To process inbound emails securely, you must validate incoming webhooks to verify their authenticity and prevent spoofing. This ensures that only legitimate email.received events trigger your backend workflows and automated routing.

What is the best way to retrieve email attachments from an inbound serverless webhook?

Retrieving email attachments requires validating the inbound webhook event first, then using the appropriate API to fetch full message content and attachments on demand. This avoids manual mailbox parsing and enables reliable serverless email processing.

Can I use inbound email webhooks for automated support ticket creation?

Inbound email webhooks are ideal for automated ticket creation and support routing. By verifying secure email.received events and extracting message content, you can programmatically route incoming emails to generate support tickets.

Do I need to parse raw mailbox files to extract inbound email content?

No, you do not need to parse raw mailbox files to extract inbound email content. By validating webhooks and retrieving full message content via API, you bypass manual mailbox parsing and build reliable email-driven workflows.

Why does my inbound email routing fail to access full message content?

Inbound email routing fails to access full message content if webhook verification is incomplete or content retrieval is not properly configured. You must validate events and explicitly fetch email bodies and attachments on demand.