Brevo
Send Brevo email and SMS and manage contacts, lists, and delivery activity from Swarmz
Connect Brevo when a project needs transactional email, transactional SMS, contact updates, or a delivery-status view. The generated app calls Brevo through the connector gateway; the Brevo API key stays server-side.
Brevo is a shared workspace connection. Sends and contact changes use the connected Brevo account for every app user permitted by the generated app.
Availability
A Swarmz administrator must show Brevo under Platform config > Integrations. Brevo does not require a Swarmz OAuth application.
Connect Brevo
- In Brevo, create an API key under SMTP & API > API Keys. Use a dedicated key for the project. Brevo documents API key creation.
- Verify the sending domain and sender in Brevo before testing email.
- In the Swarmz project, open Settings > Integrations and select Brevo.
- Select Add connection, enter the key in API key, and select Save connection.
Swarmz validates the key against the Brevo account endpoint and stores it encrypted.
Available operations
| Operation | What it does | Limit per minute |
|---|---|---|
send_email | Sends transactional email with text, HTML, or an existing template | 20 |
send_sms | Sends one transactional SMS to an E.164 number | 10 |
upsert_contact | Creates or updates one contact and optional list memberships | 20 |
list_contacts | Lists contacts with bounded pagination | 30 |
list_lists | Lists contact lists with bounded pagination | 30 |
list_email_events | Reads bounded email activity for up to 90 days | 30 |
Sends and contact updates require allow-once approval. Lists and delivery events are reads. SMS requires a Brevo account and destination that support the channel.
Ask the AI to use Brevo
- “Send the password-reset template through Brevo and show a useful error when the send is rejected.”
- “Add this opted-in customer to our newsletter list without creating duplicates.”
- “Build an email delivery panel showing delivered, bounced, and deferred events for the past seven days.”
- “Send an order-ready SMS to the E.164 number saved on the order.”
The AI requests Brevo when the feature first needs real sending or contact data. It keeps sends in generated server code and does not expose the API key to a browser.
Verify Brevo
- Send an email to a test inbox from a verified sender.
- Confirm the message in Brevo transactional logs and in the inbox.
- Upsert a test contact, then find it in the contact list.
- Read email events and confirm the test message appears with its current state.
- If SMS is enabled, send to a controlled test number and confirm it in Brevo logs.
Troubleshoot and recover
A send can fail even when setup succeeds. Check sender verification, template ID, account credit, SMS availability, and destination format. Delivery events describe provider processing; they do not prove that a person read a message.
To rotate the key, create a replacement in Brevo, update the Swarmz connection, and run list_lists before revoking the old key. To stop sending, remove the connection in Swarmz and revoke its key in Brevo.