Connect your app to Brevo

Connect your app to Brevo to send transactional and marketing emails, manage contacts and lists, and trigger communication workflows from your Lovable app.

Brevo is a customer communication platform for email, SMS, contacts, and marketing automation. It’s designed for apps that need transactional or marketing messaging, contact management, and multi-channel outreach as part of the product experience.

Brevo is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps.

With Brevo, your app can:

• Send transactional and marketing email
• Manage contacts, lists, and segmentation
• Trigger SMS and WhatsApp campaigns when supported by your Brevo account
• Track delivery and campaign performance events in Brevo

Brevo is a good fit when your app needs branded, high-volume, or multi-channel messaging beyond what Lovable’s built-in email provides, or when you already manage contacts and campaigns in Brevo.

For standard transactional emails (signup confirmations, password resets, receipts, internal notifications), use the built-in Lovable Emails.

Reach for the Brevo connector when you need marketing campaigns, contact lists, SMS/WhatsApp, lifecycle automation, or you already manage your messaging in Brevo.

Common use cases and example apps

Example app	Example prompt	Description
Order confirmations and updates	Use Brevo to send order confirmation emails and shipping updates after checkout.	Send transactional notifications from app events. The app triggers Brevo email sends whenever order status changes.
CRM-driven outreach app	Use Brevo and build a dashboard that syncs leads into Brevo lists and sends targeted campaigns.	Keep contacts and campaigns connected to product actions. The app updates contact attributes and list membership before launching campaigns.
Onboarding lifecycle app	Use Brevo to send a welcome sequence over email and SMS when users sign up.	Automate onboarding communication across channels. The app enrolls users in Brevo workflows based on signup and activation milestones.
SMS reminders and alerts	Use Brevo to send SMS reminders 24 hours before each booking and one-time codes on login.	Deliver time-sensitive messages over SMS. The app sends scheduled or event-driven SMS through Brevo (where SMS is enabled on the account).
Internal alerts app	Use Brevo to send internal alert emails for failed payments or account risk events.	Deliver operational alerts quickly to internal teams. The app formats event data and sends notifications through Brevo.
Newsletter and announcements	Use Brevo to collect subscribers and send weekly product updates from my app.	Run recurring communication from one workflow. The app captures opt-ins, stores segmentation fields, and triggers campaign sends.

How to connect Brevo

Workspace admins and owners can connect Brevo.

You can create multiple Brevo connections using different API keys, which is useful for separating environments (for example, development and production), enforcing different feature scopes, or managing rate limits.

When the connection is created, Brevo becomes available across all projects in the workspace.

Prerequisites

Before connecting Brevo, make sure you have:

• A Brevo account
• A Brevo REST API key that starts with xkeysib-
• Lovable workspace owner or admin role

Requests made through this connector are billed by Brevo based on your Brevo plan and usage. Billing is handled by Brevo, not Lovable.

Step 1: Create a Brevo API key

A Brevo REST API key lets your Lovable app authenticate with the Brevo API. You can create multiple keys with different permissions.

To create an API key in Brevo:

1. Open Brevo API key settings

   Sign in to Brevo and open Settings → SMTP & API → API keys.

2. Generate a new API key

   Click Generate a new API key.

   • Give the key a descriptive name, for example Lovable integration.
   • Choose the permissions or scopes the key should have based on what your app needs (for example transactional email, contacts, SMS).
   • Click Generate.
3. Copy and store the key

   Copy the key and store it securely. Brevo API keys start with xkeysib-.

Your API key functions like a password. Keep it secure and never share it publicly. You’ll need it in the next step.

See Brevo documentation for detailed instructions: Brevo API reference.

Step 2: Connect Brevo to Lovable

You can create multiple connections using different API keys.

1. Open Brevo in Connectors

   Go to Connectors and select Brevo.

2. Add a connection

   Click Add connection.

3. Configure the connection

   1. Display name: name the connection, for example Brevo Prod.
   2. API key: paste your Brevo API key (xkeysib-).
   3. Who can access this connection: keep access limited to specific people or invite the entire workspace. See Who can manage connections for more information.
4. Connect

   Click Connect.

When connected, your Lovable apps can start sending email and SMS, managing contacts, and using Brevo’s other API features.

Limitations

The Brevo connector cannot:

• Receive incoming Brevo webhooks or delivery events directly through the connector (you can poll Brevo’s events APIs instead, or configure webhooks to a Brevo-side endpoint outside Lovable)
• Support per-end-user Brevo authentication (each connection uses a single shared API key, scoped to the workspace)
• Refresh or revoke credentials automatically. To rotate, generate a new API key in Brevo and update the Lovable connection before app workflows can send requests again
• Send SMS or WhatsApp messages on accounts where those channels are not enabled or have no available credits. Feature availability depends on your Brevo account, plan, and enabled channels.

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.