Resend is launching inbound emails

7 hours ago 2

Resend started by modernizing the way you send emails.

Today, we're making it easy for you to receive emails as well.

Inbound unlocks entirely new use cases like:

Replying to in-app emails
Processing forwarded attachments
Receiving support emails from users

How does it work?

First, determine the email address you want to use. You can either:

Use your team's default inbound domain (e.g. <your-alias>@<id>.resend.app)
Set up a custom domain (e.g. example.com)

Resend processes all incoming emails to the provided address and then:

Parses the email content as JSON
Stores the attachment file(s)
Sends a JSON payload to an endpoint of your choice

Getting started

Here's how to start receiving emails using Resend.

1. Get your email address

To help you get started quickly, Resend provides a .resend.app address, which is automatically created for you.

To find your Resend domain:

Go to the Receiving Emails page.
Click the more options button and select Inbound address.

Send emails to your inbound address and Resend will process them and send a JSON payload to your webhook.

2. Configure webhook

In your application, create a new route that can accept POST requests.

Next, create a new webhook to receive events.

Enter your endpoint URL and select the email.received event.

3. Receive email events

Once you receive the email event, you can process the email and attachments metadata.

View received emails

All inbound emails are visible on the emails page. Resend will store your emails even if you don't configure a webhook, or if your webhook endpoint is down.

Emails can be filtered by their to, from, and subject fields. Click on an email to see its full details, including the HTML, Plain Text, and any attachments.

Process forwarded attachments

Inbound email flows often involve processing attachments.

Users can forward airplane tickets, receipts, and expenses to you. Then, you can extract key information from attachments and use that data.

To do this, call the Attachments API when you receive the webhook event. That API will return a list of attachments with their metadata and a download_url that you can use to download the actual content.