Skip to content
Email providers

Autocloz + Brevo

Brevo (formerly Sendinblue) connects to Autocloz as an SMTP relay mailbox. Choose Email service → Brevo on the Mailboxes page, enter the from-address, and paste an SMTP key from Brevo's SMTP & API page. Autocloz logs in to smtp-relay.brevo.com on port 587 using your Brevo account email as the username, tests the login, then saves. Brevo delivers the mail; replies go to your real inbox, which you can connect separately so they appear in the Unibox.

Autocloz and Brevo integration
Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core

What you can do with Brevo

Brevo plugs into the Email stack — connect via oauth or smtp/imap, scoped to your workspace.

SMTP key, not API key

Brevo issues separate API keys and SMTP keys. The relay needs the SMTP key from SMTP & API → SMTP.

Account email as login

The Brevo preset uses your Brevo login email as the SMTP username, which is what Brevo's relay expects.

Probe before saving

A wrong key fails at connect time with Brevo's SMTP response, instead of on the first campaign send.

How to connect Brevo

Connect via OAuth or SMTP/IMAP — you keep control of the account, the spend and the data boundary.

  1. 1

    Verify your sender or domain in Brevo

    Add and authenticate the domain you send from under Senders, Domains & Dedicated IPs.

  2. 2

    Generate an SMTP key

    In Brevo go to SMTP & API → SMTP and generate a key. Note the SMTP login shown there.

  3. 3

    Connect it in Autocloz

    Mailboxes → Connect mailbox → Email service → Brevo. Enter from-address, from-name and the SMTP key.

  4. 4

    Check the login matches

    If Brevo's SMTP page shows a login different from your account email, use Custom SMTP with that login instead.

Settings Autocloz uses for Brevo

These values come from the Brevo preset.

  • Host: smtp-relay.brevo.com
  • Port: 587 with STARTTLS
  • Username: your Brevo account email
  • Password: an SMTP key from SMTP & API → SMTP

When the Brevo option is missing

Each email service provider in Autocloz can be switched on or off by your platform's super-admin, globally or for one workspace. If Brevo is not in the Email service list, it has been switched off. If no provider is enabled, the Email service tab does not appear at all. Trying to connect a disabled provider through the API returns a clear 403 explaining that an administrator turned it off, rather than failing silently.

Security of the stored key

The SMTP key is encrypted before it is stored and is never shown back. Autocloz rejects a pasted value that contains asterisks, because that is the masked on-screen text rather than the real key, and it refuses a second mailbox with an address already connected in the workspace.

Brevo's two kinds of keys

Brevo's dashboard offers API keys (starting xkeysib-) for its REST API and SMTP keys (starting xsmtpsib-) for the relay. Autocloz sends over SMTP, so it needs the SMTP key. Pasting an API key is the most common reason a Brevo connection fails with a 535 error.

Brevo's free plan caps daily sends. Autocloz does not know your Brevo plan, so set the mailbox's daily limit to match it, or campaign sends above the cap will be refused by Brevo. The sending limits guide compares common providers.

What Autocloz adds on top of Brevo

Brevo handles delivery. Autocloz handles who gets which message and when: multi-step sequences, per-mailbox pacing, stop-on-reply (when replies reach a connected inbox), unsubscribe handling and tracking. Brevo's own marketing automation, contact lists and templates are not synced. Your contacts live in the Autocloz CRM; see email outreach.

What Brevo does not do in Autocloz

  • No syncing of Brevo contacts, lists or templates.
  • No reading of replies through Brevo.
  • No Brevo transactional-API sending; SMTP only.

Troubleshooting Brevo

535 authentication error.
You pasted an API key (xkeysib-) instead of an SMTP key (xsmtpsib-).
Brevo rejects the sender.
The from-address is not a verified sender in Brevo.

Part of the Email stack

Brevo is one of the providers behind the Email channel. All mailboxes share the same sequencing, unified inbox, and deliverability tooling regardless of provider.

Explore the Email feature

Related integrations

Frequently asked

Is Brevo the same as Sendinblue?

Yes. Sendinblue renamed itself Brevo; the relay host is smtp-relay.brevo.com.

Can Brevo send my cold sequences?

Technically yes, but check Brevo's acceptable-use policy on unsolicited mail before you do.

Does Brevo's free plan work?

It works for low volumes. Brevo's free plan has a daily sending cap, so set the mailbox's daily limit at or below it.

Run Brevo inside Autocloz

Bring your own account, plug it into the Email channel, and keep a free-forever CRM for 3 users.