Resend

Resend is a modern email API designed for developers with a clean, intuitive interface.

Prerequisites

Before configuring Resend in Notiflows, you need:

A Resend account
A verified domain
An API key with sending access

Configuration

Field	Required	Description
API Key	Yes	Resend API key with sending access
From Email	Yes	An email address on your verified domain
From Name	No	Display name shown to recipients (e.g., `My App`)

Step 1: Add and verify a domain

Resend requires you to verify the domain you send from by adding DNS records.

Log in to the Resend dashboard
In the left navigation, click Domains
Click Add Domain
Enter your domain name — Resend recommends using a subdomain like updates.yourdomain.com to separate transactional email from your root domain's reputation
Resend provides DNS records to add:
- SPF (TXT record) — authorizes Resend to send from your domain
- DKIM (TXT record) — provides a public key to verify email authenticity
Add both records to your DNS provider
Return to the Resend dashboard and click Verify

DNS changes typically propagate within a few hours but can take up to 72 hours. If the domain isn't verified after 72 hours, the status changes to "failed" and you'll need to re-add it.

Step 2: Create an API key

In the Resend dashboard, click API Keys in the left navigation
Click Create API Key
Enter a name (e.g., Notiflows) — maximum 50 characters
Select Sending access — this is the minimum permission needed and is recommended over full access
Optionally restrict the key to a specific verified domain
Click Create
Copy the API key immediately

Resend only shows the API key once. Copy it now and store it securely. If you lose it, you'll need to create a new key.

Step 3: Set up in Notiflows

Navigate to Channels in your project
Click Create Channel
Select Email as the channel type
Select Resend as the provider
Paste your API Key
Enter your verified From Email (must be on your verified domain) and optionally a From Name
Save the channel

Templates

Email templates support three content types:

Visual - Drag-and-drop editor for rich HTML emails
HTML - Raw HTML with full control
Plaintext - Simple text emails

Use Liquid templating for dynamic content:

Hi {{ recipient.first_name }},

{{ data.message }}

Available variable contexts:

recipient.* - Recipient user data (first_name, last_name, email, etc.)
actor.* - User who triggered the notification
data.* - Custom payload passed when triggering the notiflow