Skip to main content
Resend is an email API for developers. The Resend connector lets your Lovable app send transactional and marketing emails through your own Resend account, from a domain you have verified in Resend. It’s designed for apps that send email as part of a product workflow, such as confirmations, notifications, digests, and campaigns. Resend is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps. With Resend, your app can:
  • Send transactional emails with HTML or plain-text bodies
  • Send to multiple recipients, with cc, bcc, and reply-to addresses
  • Attach files and tag emails for tracking in Resend
  • Read the sending domains and email status in your Resend account
For standard transactional emails (signup confirmations, password resets, receipts, internal notifications), use the built-in Lovable Emails.Reach for the Resend connector when you want to send from your own verified domain, need Resend’s delivery tooling, or already manage your sending in Resend.

Common use cases and example apps

These examples show what you can build with Resend, each with a prompt to start from.

How to connect Resend

Who can create Resend connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it in Connectors → Admin settings → App + chat connectors. You can create multiple Resend connections using different API keys, which is useful for separating environments (for example, development and production) or sending from different Resend accounts. When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

Prerequisites

Before connecting Resend, make sure you have:
  • A Resend account
  • A verified sending domain in that Resend account, if you want to email people other than yourself
  • A Resend API key
  • Permission to create connections in your Lovable workspace (see Who can create connections and clients)
All email sent through this connector counts toward your Resend plan and is billed by Resend, not Lovable.

Step 1: Get a Resend API key

An API key lets your Lovable app authenticate with the Resend API. Resend keys have one of two permission levels: Full access keys can manage every resource in your account, and Sending access keys can only send emails, optionally from a single domain. To create a Resend API key:
1

Open your Resend account

Sign in to Resend and open API Keys.
2

Create a key

Click Create API Key. Give it a descriptive name, for example Lovable integration, and choose the permission level. Sending access is enough for an app that only sends email. Choose Full access if your app also needs to read domains or email status.
3

Copy the key

Copy the key and store it securely. Resend shows it only once. Keys start with re_.
Your API key functions like a password. Keep it secure and never share it publicly. You’ll need it in the next step.
See Resend documentation for more: API keys and the Resend API reference.

Step 2: Connect Resend to Lovable

You can create multiple connections using different API keys.
1

Open Resend in Connectors

Open Connectors and select Resend. For the other places to open the catalog from, see Where to find connectors.
2

Add a connection

Click Add connection.
3

Configure the connection

  1. Display name: name the connection, for example Resend Prod. This name is only used inside Lovable to identify the connection.
  2. API Key: paste your Resend API key. Lovable accepts keys that start with re_.
4

Choose who can use this connection

Under Who can use this connection, decide who in your workspace can use the connection. You start as the only person with access:
  • Only you (default): leave the access list as is; only you can use the connection and its associated data.
  • Invite specific people: add workspace members by email; only you and the people you add can use the connection and its associated data.
  • Invite entire workspace: click Invite entire workspace to make the connection available to everyone in your Lovable workspace.
See Who can use connections and clients for more information.
5

Connect

Click Connect. Lovable verifies the key against the Resend API before saving the connection. Both Full access and Sending access keys pass this check.
When connected, anyone building in a project can ask Lovable in chat to link their project to Resend (based on configured connection-level access). Your Lovable apps can then send email through your Resend account.

Sending from your domain

Resend delivers email to your app’s users only from a domain you have verified in Resend. Resend’s shared test address, onboarding@resend.dev, delivers only to the email address of the Resend account owner, so it works for your own tests but not for real recipients. Before sending to users, add your domain in Resend and confirm it shows as verified, with the DNS records Resend asks for added at your DNS provider. The connector does not configure DNS or verify domains for you. When prompting Lovable, mention the address you want to send from (for example, hello@mydomain.com) so the generated app uses it consistently.

Limitations

The Resend connector cannot:
  • Verify or register sending domains for you. Configure these in Resend first.
  • Receive Resend event webhooks through the connector. Configure webhooks in Resend to an endpoint outside Lovable, or read email status from the Resend API instead.
  • Support per-end-user Resend login. Each connection represents a single Resend account shared across all projects linked to it.

Manage your connection

Connections are managed from Connectors: select , then open the connection.
  • Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
  • Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.