resend-inbound

To process inbound emails using Resend webhooks, you must first configure a receiving domain and a webhook endpoint. The skill then validates incoming webhook events, retrieves the email body, and handles any attachments automatically.

Webhook verification for Resend inbound email ensures that incoming events genuinely originate from Resend. This skill uses the Resend SDK features to validate webhook signatures before processing the email content or attachments.

Yes, you can forward inbound emails with attachments to downstream services. After retrieving the email content and attachments on demand, the workflow supports forwarding the complete payload to your designated external endpoints.

You need to configure an inbound domain and set up a webhook endpoint to receive inbound emails with Resend. This establishes reliable delivery routing so the skill can validate events and extract the email body and attachments.

You retrieve email content and attachments from an inbound message on demand after the webhook is validated. The skill extracts the email body and processes attachments securely as part of its centralized content retrieval workflow.

If your Resend inbound email webhook is not processing attachments, ensure your receiving domain is properly configured and the webhook signature is successfully validated before attempting content retrieval and attachment extraction.