- You only need Lovable Cloud authentication emails from your custom domain. In that case, see Custom emails.
- You need each end user to connect their own email provider account separately. Shared connectors are workspace-level, not per-end-user connections.
Common use cases and example apps
| Example app | Example prompt | Description |
|---|---|---|
| Order updates app | Send an order confirmation email through Resend after checkout. | Send transactional confirmations when users complete an action. |
| Booking platform | When a booking is created, email the customer and the internal team through Resend. | Trigger multi-recipient operational emails from one workflow. |
| User onboarding | Send a welcome email series through Resend when a new account is created. | Automate onboarding touchpoints tied to app events. |
| Newsletter | Create a newsletter signup flow that stores subscribers and sends campaigns with Resend. | Build list and campaign flows using your Resend setup. |
How Resend connections work
Each Resend connection uses one Resend API key. Within your Lovable workspace:- You can create multiple Resend connections.
- Each connection is a separate credential setup.
- Multiple projects can use the same connection.
How to connect Resend
Workspace admins and owners can connect Resend. When a connection is created, Resend becomes available across all projects in the workspace.Requirements and billing
- Available on: all plans
- Connector roles: workspace admins and owners can create and manage Resend connections
- Additional admin controls: on Business and Enterprise plans, workspace admins and owners can enable or disable shared connector availability at the workspace level
- Prerequisites: a Resend account and a Resend API key
- Recommended for production: verify your sending domain in Resend before high-volume sending
Resend usage and pricing are owned by your Resend account. Charges for email sending are billed by Resend, not by Lovable.
Set up your Resend connection
FAQ
Do I need a Resend account to use this connector?
Do I need a Resend account to use this connector?
Yes. You need your own Resend account and API key to create a Resend connection in Lovable.
Who pays for email sending with this connector?
Who pays for email sending with this connector?
Email sending through this connector is billed by Resend, based on your Resend plan and usage.
Can I create multiple Resend connections?
Can I create multiple Resend connections?
Yes. You can create multiple connections, for example to separate staging and production environments.
Can end users connect their own Resend accounts inside my app?
Can end users connect their own Resend accounts inside my app?
Not through this shared connector flow. Shared connectors are configured at workspace level.
What should I check first if emails are not sending?
What should I check first if emails are not sending?
Verify your API key, confirm sender/domain setup in Resend, and check Resend activity/logs for rejected or failed sends.
Limitations
- A Resend shared connector is a workspace-level credential, not a per-user email login flow.
- For production reliability, verify your sending domain in Resend and monitor delivery/rejection activity in Resend logs.
- If a connected project stops sending after connector changes, open the connection and confirm it is still linked to the project.
How to unlink projects from a connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects. To unlink projects:
When unlinked, those projects will no longer have access to through this connection. If a project needs again, you can link it to any available connection.