Mailjet lifecycle email automation with GetFluxly

GetFluxly captures product events, builds unified customer profiles, and fires automations on the rules you define. Mailjet handles the actual delivery from the verified sending domain you control through the Mailjet SMTP relay. Your sender reputation and sending history stay in your Mailjet account.

When to use Mailjet

Pick Mailjet when you want a well-supported European ESP with strong deliverability tooling and the option to keep data inside the EU. Mailjet ships a full SMTP relay, so teams that already rely on SMTP can adopt it without changing send architecture. The pricing model scales on volume, which works well for SaaS products that start small and grow into meaningful send counts over time.

Mailjet is also a natural fit if your customer base is concentrated in Europe and you want to point to a provider that runs EU infrastructure in your privacy policy. If you are already on AWS and want the lowest possible per-message cost, see the Amazon SES guide instead. For the fastest zero-configuration DX, see the Resend guide.

Before committing to a provider, the email deliverability for SaaS post covers what actually moves inbox placement so you can pick the right stack for your volume and region.

Requirements before connecting

A Mailjet account on any plan, a domain you can publish DNS records on, and the Primary API Key plus its Secret Key from the Mailjet dashboard. On the GetFluxly side: a project, a server token (gflux_secret_live_...), and access to Settings → Email providers.

New Mailjet accounts start in a restricted state until the first domain is verified. Domain verification unlocks production sending and is required before GetFluxly can dispatch through the connection.

Verify your sending domain

In the Mailjet dashboard, open Sender domains & addresses and click Add a domain. Enter the apex of the domain you want to send from (for example yourdomain.com). Mailjet presents a TXT record for ownership verification, once that propagates, the domain status changes to Authenticated.

Verifying the apex covers every from address under it, so you don't need to verify each mailbox separately.

Add SPF, DKIM, and DMARC

These records live on your domain's DNS, not on GetFluxly. They tell receiving mailboxes that Mailjet is allowed to send on your behalf and what to do when alignment checks fail.

SPF

Add a TXT record at the apex that includes Mailjet. If you already have an SPF record, merge the include: rather than publishing a second SPF record on the same name (two SPF records on one host cause automatic validation failure).

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

DKIM

Mailjet generates a DKIM TXT record when you verify your domain. The selector and value are unique to your account. Copy them exactly from the Mailjet Sender domains & addresses screen.

Type:   TXT
Host:   mailjet._domainkey.yourdomain.com
Value:  <DKIM public key, copy from Mailjet>

DMARC

DMARC tells receivers what to do if SPF and DKIM alignment both fail. Start with p=none while you confirm that legitimate mail passes, 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 Mailjet credentials

Mailjet authenticates SMTP connections with an API Key and Secret Key pair. Both are required for the SMTP relay.

Retrieve the Primary API Key and Secret Key

In the Mailjet dashboard, open Account settings → API keys. Under Primary API Key, click Generate Secret Key. A dialog displays both the API Key and the Secret Key. Copy both immediately as Mailjet only shows the Secret Key once. Store both in a secrets manager before leaving the page.

Connect Mailjet in GetFluxly

Because a native Mailjet connector is not live yet, connect Mailjet through GetFluxly's Custom SMTP connector. Open your GetFluxly project, go to Settings → Email providers, click Add provider, and choose Custom SMTP. Use these Mailjet 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": "Mailjet Production",
    "from_email": "hello@yourdomain.com",
    "from_name": "Acme",
    "smtp_host": "in-v3.mailjet.com",
    "smtp_port": 587,
    "smtp_secure": "starttls",
    "username": "YOUR_MAILJET_API_KEY",
    "password": "YOUR_MAILJET_SECRET_KEY"
  }'

Handle bounces and complaints

While sending through the Custom SMTP path, manage suppressions and bounce handling inside your Mailjet dashboard. Mailjet tracks hard bounces, spam complaints, and blocked events at the account level under Account settings → Event tracking (callbacks). Use Mailjet's built-in suppression list to keep your sending reputation healthy.

Automatic ingestion of bounce and complaint signals into GetFluxly profiles and suppression lists arrives with the native Mailjet connector when it ships. Until then, periodically export your Mailjet suppression list and remove those contacts from your GetFluxly automations manually. For more context on why a clean suppression loop matters, see the lifecycle email automation guide.

Test your first lifecycle email

The verify endpoint dispatches a one-shot message through your Mailjet connection. Use it to confirm the wiring 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, set up a one-step automation in GetFluxly: when user fires signed_up send the welcome email through Mailjet, then trigger the event from your staging app. The send appears in GetFluxly's send log within a few seconds. See pricing for the plan that matches your expected send volume.

Common errors

Authentication failed. The API Key or Secret Key is wrong, or the Secret Key was never copied before the page was closed. Go to Account settings → API keys in Mailjet, generate a new Secret Key, and update the GetFluxly Custom SMTP record with the fresh credentials.

From address not a verified sender. The address in from_email is not under an authenticated sender domain. Confirm the domain status reads Authenticated in Mailjet and that DKIM is green before retrying.

Mail going to spam. Almost always missing or misconfigured DMARC, or a sending domain with no warm-up history. Confirm the DMARC record is published on _dmarc.yourdomain.com and ramp send volume gradually over the first two weeks.

Mailjet daily send limit hit. Free Mailjet accounts cap at 200 emails per day. Upgrade your Mailjet plan to lift the limit before going live with lifecycle automations.

FAQ