- Send transactional and marketing email
- Manage contacts, lists, and segmentation
- Trigger SMS and WhatsApp campaigns when your Brevo account has those channels enabled
- Track delivery and campaign performance events in Brevo
Common use cases and example apps
These examples show what you can build with Brevo, each with a prompt to start from.How to connect Brevo
Who can create Brevo 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 Brevo connections using different API keys, which is useful for separating environments (for example, development and production) or managing rate limits. 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 Brevo, make sure you have:- A Brevo account
- A Brevo REST API key that starts with
xkeysib- - Permission to create connections in your Lovable workspace (see Who can create connections and clients)
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 separate keys for different environments or apps. To create an API key in Brevo:1
Open Brevo API key settings
Sign in to Brevo and open SMTP & API → API keys.
2
Generate a new API key
Click Generate a new API key, give it a descriptive name, for example
Lovable integration, and click Generate.3
Copy and store the key
Copy the key and store it securely. Brevo API keys start with
xkeysib-.Step 2: Connect Brevo to Lovable
You can create multiple connections using different API keys.1
Open Brevo in Connectors
Open Connectors and select Brevo. 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
- Display name: name the connection, for example
Brevo Prod. This name is only used inside Lovable to identify the connection. - API key: paste your Brevo API key. Lovable accepts keys that start with
xkeysib-.
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.
5
Connect
Click Connect. Lovable verifies the key against the Brevo API before saving the connection.
Limitations
The Brevo connector cannot:- Receive incoming Brevo webhooks or delivery events through the connector. Poll Brevo’s events APIs instead, or configure webhooks in Brevo to an endpoint outside Lovable.
- Refresh or revoke credentials automatically. To rotate, generate a new API key in Brevo and update the Lovable connection.
- 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.
- Support per-end-user Brevo login. Each connection represents a single Brevo 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.