Skip to main content
Resend is an email API platform for sending and managing email delivery. The Resend app + chat connector lets your Lovable apps call Resend from your workspace using a managed workspace-level connection. Resend is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps. Each Resend connection uses your own Resend API credentials. After it is connected, projects in your workspace can use the connection to send emails through your Resend account. Use the Resend connector when your app needs to send email as part of product workflows, such as confirmations, notifications, or campaign-related messages. Use another path when:
  • You only need your app’s authentication emails sent from your custom domain. In that case, see Custom emails.
  • You need each end user to connect their own email provider account separately. App + chat connectors are workspace-level, not per-end-user connections.

Common use cases and example apps

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.
This helps you separate environments, such as staging and production.

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 choose who can create connections per connector, as described in Who can create connections and clients
  • 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.
App + chat connector connections are workspace-level. Anyone in the workspace who can use connected projects can use the Resend connection in those projects.

Set up your Resend connection

1

Open the connector

Open Connectors and select Resend.
2

Add a connection

Click Add connection.
3

Name the connection

In Display name, enter a clear name, for example Resend Prod or Resend Staging.
4

Enter credentials

Paste your Resend API key in the authentication field.
5

Create the connection

Click Create.
6

Use it in your app

Prompt Lovable to add or update email flows that use Resend, then test with real recipient addresses you control.

FAQ

Yes. You need your own Resend account and API key to create a Resend connection in Lovable.
Email sending through this connector is billed by Resend, based on your Resend plan and usage.
Yes. You can create multiple connections, for example to separate staging and production environments.
Not through this app + chat connector flow. App + chat connectors are configured at workspace level.
Verify your API key, confirm sender/domain setup in Resend, and check Resend activity/logs for rejected or failed sends.

Limitations

  • A Resend app + chat 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.

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.