Brevo lifecycle email automation with GetFluxly

Send behavior-triggered lifecycle email through your Brevo account. GetFluxly captures product events, builds unified customer profiles, and fires automations on the rules you define. Brevo handles delivery from the sender domain you authenticate. Your sending reputation stays in your Brevo account. Brevo was previously known as Sendinblue; the SMTP credentials and DNS setup are identical under both names.

When to use Brevo

Brevo is a strong fit if you are already using Brevo for marketing campaigns and want to pipe GetFluxly's behavior-triggered lifecycle email through the same sending infrastructure. Keeping your sending domain, reputation, and suppression data in one place simplifies operations. Brevo's SMTP relay is also a common pick for teams in Europe because Brevo is GDPR-native and offers EU-based data storage.

If you want to compare GetFluxly and Brevo as automation platforms rather than use them together, see the GetFluxly vs Brevo comparison.

Requirements before connecting

A Brevo account on any plan that includes transactional email (the Free plan includes 300 emails per day via SMTP), a domain you can publish DNS records on, and a Brevo SMTP key. On the GetFluxly side: a project, a server token (gflux_secret_live_...), and access to Settings → Email providers.

Authenticate your sending domain

In Brevo, open Settings → Senders and IPs → Domains and click Add a domain. Enter the apex domain you want to send from (for example yourdomain.com). Brevo provides a set of DNS records: a TXT record for domain ownership verification, a DKIM TXT record, and an SPF include value. Publish all of them at your DNS provider and click Authenticate in Brevo once propagation completes.

Once the domain is authenticated, any sender address under that domain can be used as the From: in GetFluxly. You still need to add individual sender addresses in Settings → Senders and IPs → Senders so Brevo recognises them as approved senders.

Add SPF, DKIM, and DMARC

These records live on your domain's DNS, not on GetFluxly. They tell receiving mailboxes that Brevo is allowed to send on your behalf and what to do if alignment fails.

SPF

Add a TXT record at the apex that includes the Brevo sending servers. If you already have an SPF record, merge the include: rather than publishing two SPF records on the same name.

Type:   TXT
Host:   yourdomain.com
Value:  v=spf1 include:spf.brevo.com -all

DKIM

Brevo issues a single TXT record for DKIM. The exact host and value are shown in the domain authentication screen after you add your domain. The host typically looks like mail._domainkey.yourdomain.com.

Type:   TXT
Host:   mail._domainkey.yourdomain.com
Value:  k=rsa; p=<public key from Brevo>

DMARC

Start with p=none while you confirm legitimate mail passes SPF and DKIM alignment, then tighten the policy over time.

Type:   TXT
Host:   _dmarc.yourdomain.com
Value:  v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; fo=1

Create a Brevo SMTP key

In Brevo, open Settings → SMTP and API → SMTP and click Generate a new SMTP Key. Give the key a name like getfluxly-production and copy the value. The key string is your SMTP password. Your Brevo login email address is the SMTP username.

The Brevo SMTP relay host is smtp-relay.brevo.com on port 587 with STARTTLS.

Connect Brevo through Custom SMTP in GetFluxly

Because a native Brevo connector is not yet live, connect Brevo through the Custom SMTP connector. In GetFluxly, open Settings → Email providers, click Add provider, choose Custom SMTP, and enter the following Brevo SMTP settings:

Or call the API directly:

curl -X POST https://api.getfluxly.com/v1/projects/PROJECT_ID/email-providers \
  -H "Authorization: Bearer gflux_secret_live_REPLACE_ME" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "smtp",
    "display_name": "Brevo Production",
    "from_email": "hello@yourdomain.com",
    "from_name": "Acme",
    "smtp_host": "smtp-relay.brevo.com",
    "smtp_port": 587,
    "smtp_secure": "starttls",
    "username": "you@example.com",
    "password": "xsmtpsib-..."
  }'

Handle bounces and complaints

Brevo delivers hard bounce and spam complaint events through its transactional webhook system. Wire them to GetFluxly so the suppression list stays current and affected contacts are tagged in the unified profile, ensuring future segments exclude them automatically.

1. In GetFluxly, copy the project webhook URL from Settings → Webhooks → Brevo. It looks like https://api.getfluxly.com/v1/webhooks/brevo/<project_id>.
2. In Brevo, open Transactional → Settings → Webhooks (or navigate to the transactional webhooks page in the dashboard) and add the GetFluxly URL.
3. Select the Hard bounce and Spam event types at minimum. Adding Delivered is optional but gives GetFluxly confirmed delivery timestamps.

Hard bounces suppress the address permanently. Brevo also tracks soft bounces and removes the address after several consecutive soft bounces, and GetFluxly mirrors that via the webhook.

Test your first lifecycle email

The verify endpoint dispatches a one-shot message through your Brevo connection. Use it to confirm the wiring is correct before pointing an automation at the provider.

curl -X POST https://api.getfluxly.com/v1/email-providers/PROVIDER_ID/test \
  -H "Authorization: Bearer gflux_secret_live_REPLACE_ME" \
  -H "Content-Type: application/json" \
  -d '{ "to": "you@yourdomain.com" }'

For an end-to-end behavior-triggered test, create a one-step automation in GetFluxly: when user fires signed_up → send the welcome email through Brevo, then fire the event from your staging app. The send appears in the GetFluxly send log and in the Brevo transactional logs within seconds.

Common errors

535 Authentication failed. The SMTP credentials are wrong. Confirm you are using your Brevo login email as the username and a valid SMTP key (not your account password) as the password. Regenerate the key in Brevo if needed and update the GetFluxly record.

550 The from address is not a registered sender. The address in from_email is not added as a sender in Brevo. Open Settings → Senders and IPs → Senders, add the address, and confirm ownership.

Mail landing in spam despite DKIM passing. Check that DMARC is published on _dmarc.yourdomain.com and that the domain is showing as fully authenticated in Brevo. Deliverability also improves with gradual volume ramp-up over the first two weeks on any new sending domain.

Free plan daily limit reached. Brevo's Free plan allows 300 emails per day. If your lifecycle automations exceed that, upgrade to a paid Brevo plan to lift the daily cap.

FAQ