close
Skip to main content
Resend is an email API for sending and tracking email delivery. The Resend connector lets your Lovable app send email through your Resend account. It’s designed for apps that send email as part of a product workflow, such as confirmations, notifications, and onboarding messages. Resend is available as an app + chat connector: one shared connection that works in the project chat while you build and in your published apps. With Resend, your app can:
  • Send transactional emails when something happens in your app, such as a sign-up, a checkout, or a form submission
  • Send HTML or plain-text emails to one or more recipients from your own verified domain
  • 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.Lovable Emails can also send from your own domain. Use the Resend connector when you 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 Business and Enterprise plans, Who can create connections and clients starts at Admins. Some Enterprise workspaces start at No one, which disables the connector. An admin or owner changes it in Connectors → Admin settings → App + chat connectors. When adding a connection, you can choose between:
  • Connect with Resend: sign in with your Resend account and approve access for your Resend team
  • Use your own credentials: bring your own Resend API key
You can create multiple Resend connections using different Resend teams or API keys, which is useful for separating environments, such as staging and production. 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 the project chat to link their project to it.

​
Prerequisites

Before connecting Resend, make sure you have:
Emails sent through this connector count toward your Resend plan. Billing and quota are handled directly by Resend, not Lovable.
Follow the setup steps below based on how you want to connect Resend.
Choose this option for the fastest setup, with no API key to create. Connect on the connector page skips the connection form and creates a connection with Full access that is private to you. You can share the connection later from its settings.
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

Connect and authorize

Click Connect on the connector page. In the Resend window that opens, sign in if prompted and authorize the app. If your browser blocks pop-ups, Lovable redirects you instead. You’ll be redirected back to Lovable with a confirmation.

​
Choose scopes and sharing before you connect

To choose Sending access, or to name or share the connection while you create it, use the connection form. On the connector page, open More options and select App + chat connector. Under Configure connection, select Connect with Resend, then choose the scopes:Select Sending access and clear Full access only if your app never reads from Resend. A Sending access connection can’t read your sending domains or email status. Keep at least one scope selected. For full scope documentation, see Resend’s scope reference.Set who can use the connection under Sharing, then click Connect at the bottom of the form and authorize in the Resend window.A connection made with your Resend account refreshes its access automatically. If Lovable can’t refresh it, for example because the access was revoked in Resend, the connection shows as expired and you reconnect it. Deleting the connection in Lovable also revokes Lovable’s access in your Resend account.
When connected, anyone building in a project can ask Lovable in the project 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. Resend rejects sends from it to anyone else, so it works for the owner’s own tests but not for real recipients. Before sending to users, add your domain in Resend, add the DNS records Resend lists at your DNS provider, and wait until the domain shows as verified on the Domains page. When prompting Lovable, mention the address you want to send from (for example, hello@mydomain.com) so your app uses it consistently.

​
Limitations

The Resend connector cannot:
  • Create a Resend account or verify your sending domain. You add the domain and its DNS records in Resend.
  • Receive Resend event webhooks through the connector. Point Resend webhooks at your app’s own backend endpoint, or read email status from the Resend API instead.
  • Support per-end-user Resend login. Each connection represents a single Resend team shared across all projects linked to it.
  • Rotate API keys automatically. For connections that use your own API key, create a new key in Resend and update the Lovable connection.

​
Troubleshooting

Resend accepted the email, so the problem is delivery, not the connection. Open Emails in Resend and check that message’s delivery status to see why it didn’t arrive.

​
Manage your Resend connection

Connections are managed from Connectors: select Resend, then open the connection.
  • Unlink projects to remove Resend 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 Resend stop working until a new connection is added. See Delete a connection for the steps and who can delete.