DextelDocs

Connect Brevo

Formerly Sendinblue. Unsigned webhooks; Dextel creates the inbound parsing route for you through the API.

Where this lives in Dextel

Agency: Agency → Integrations → Email Service (outbound only). Sub-account: Settings → Integrations → Email Integration (outbound + inbound). The modal shows the exact webhook URLs to paste into Brevo; this page explains what to do with them.

Prerequisites

  • A Brevo account and a domain you control (you'll add DNS records).
  • Owner or admin access to the Dextel agency or sub-account.
  • Credentials you'll enter in Dextel: API key (xkeysib-…).

1. Create the API credentials

  1. Click your profile → SMTP & API → API Keys → Generate a new API key.
  2. Copy the key (starts with xkeysib-) into Dextel.

Brevo docs: API keys

2. Verify your sending domain

  1. Open Senders, Domains & Dedicated IPs → Domains → Add a domain.
  2. Add the Brevo code TXT, the DKIM TXT (mail._domainkey) and the DMARC record to your DNS.
  3. Click Authenticate this domain.

Then in Dextel enter a From email on that domain (for example hello@yourdomain.com) and a From name, and click Validate & Connect. Dextel checks the credentials against Brevo before saving.

Brevo docs: domains

3. Delivery events

Delivered, opened, clicked, bounced and spam events feed the Email Event workflow trigger and automatically unsubscribe contacts after a hard bounce or complaint. Copy the Webhook URL from the Delivery events tab in Dextel, then:

  1. Open Transactional → Settings → Webhooks → Add a new webhook.
  2. Paste <your delivery-events webhook URL> as the URL.
  3. Tick Delivered, Deferred, Soft bounce, Hard bounce, Blocked, Invalid email, Complaint, Opened and Clicked, then Save.
  4. Keep the URL private — Brevo doesn't sign webhooks.
This provider does not sign its webhooks. The webhook URL Dextel gives you contains a private token that authenticates each post — never share the URL.

Use Send a test email in the same tab to confirm outbound works; the events pill turns green once the first event arrives.

Brevo docs: webhooks

4. Inbound email (sub-accounts only)

Inbound turns contact replies into Inbox conversations and fires the Contact Replied — Email trigger. Mail is received at your saved From address, so when a contact hits Reply the message comes back through Brevo to Dextel. The MX record routes all mail for that domain to Brevo: if you already receive mail on the domain, send from an address on a subdomain (for example hello@mail.yourdomain.com).

DNS records

TypeHostValuePriority
MXyourdomain.cominbound1.sendinblue.com10
MXyourdomain.cominbound2.sendinblue.com20

Steps

  1. Add the two MX records below to yourdomain.com and wait for DNS to propagate.
  2. In Dextel's Inbound tab click Register with Brevo — Dextel creates the inbound parsing webhook for the domain with your API key.
  3. Send a test email to your From address.

Registered by Dextel

Brevo only exposes inbound configuration through its API, so the Inbound tab has a Register with Brevo button that creates the route with your stored key once the DNS records are live.

Limits

  • Some accounts need Inbound Parsing enabled by Brevo support before registration succeeds.

Brevo docs: inbound

Troubleshooting

  • Registration fails with a permission error — ask Brevo support to enable Inbound Parsing on the account.
  • Attachments missing — the API key must still be valid; Dextel fetches attachments from Brevo with it after the webhook arrives.
  • Still stuck? Compare with another provider on the Email Providers overview.