Envello
Flowmailer alternative

Switching from Flowmailer? Move your transactional email to Envello

A step-by-step guide: DNS setup alongside your existing records, the sending-code swap, a dual-send cutover window, and verification with 90 days of searchable logs on Pro.

Flowmailer is a Dutch company, so data location alone isn't a reason to switch. Its API works differently from Envello's: you request an OAuth2 access token with client credentials, then POST a SubmitMessage to /{account_id}/messages/submit with one recipient per message, and a flow configured in Flowmailer decides how the message is processed. Envello uses a static Bearer API key and one flat JSON body.

Before: Flowmailer Node (fetch)
const FLOWMAILER_JSON = "application/vnd.flowmailer.v1.12+json";

const tokenResponse = await fetch("https://login.flowmailer.net/oauth/token", {
  method: "POST",
  headers: { "Content-Type": "application/x-www-form-urlencoded", Accept: FLOWMAILER_JSON },
  body: new URLSearchParams({
    client_id: process.env.FLOWMAILER_CLIENT_ID,
    client_secret: process.env.FLOWMAILER_CLIENT_SECRET,
    grant_type: "client_credentials",
    scope: "api",
  }),
});
const { access_token } = await tokenResponse.json();

await fetch("https://api.flowmailer.net/" + process.env.FLOWMAILER_ACCOUNT_ID + "/messages/submit", {
  method: "POST",
  headers: { Authorization: "Bearer " + access_token, Accept: FLOWMAILER_JSON, "Content-Type": FLOWMAILER_JSON },
  body: JSON.stringify({
    messageType: "EMAIL",
    senderAddress: "[email protected]",
    headerFromAddress: "[email protected]",
    headerFromName: "Acme",
    recipientAddress: "[email protected]",
    subject: "Welcome",
    html: renderedHtml,
  }),
});
After: Envello Node (fetch)
import { Envello } from "envello";

const envello = new Envello(process.env.ENVELLO_API_KEY);

await envello.emails.send({
  from: "Acme <[email protected]>",
  to: "[email protected]",
  subject: "Welcome",
  html: renderedHtml,
});
Before: Flowmailer REST
curl -X POST https://api.flowmailer.net/$FLOWMAILER_ACCOUNT_ID/messages/submit \
  -H "Authorization: Bearer $FLOWMAILER_ACCESS_TOKEN" \
  -H "Accept: application/vnd.flowmailer.v1.12+json" \
  -H "Content-Type: application/vnd.flowmailer.v1.12+json" \
  -d '{
    "messageType": "EMAIL",
    "senderAddress": "[email protected]",
    "headerFromAddress": "[email protected]",
    "headerFromName": "Acme",
    "recipientAddress": "[email protected]",
    "subject": "Welcome",
    "html": "<p>Welcome aboard</p>"
  }'
After: Envello REST
curl -X POST https://api.envello.dev/emails \
  -H "Authorization: Bearer $ENVELLO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <[email protected]>",
    "to": "[email protected]",
    "subject": "Welcome",
    "html": "<p>Welcome aboard</p>"
  }'
Field mapping

Flowmailer fields and their Envello equivalents

FlowmailerEnvello
OAuth2 client credentials, then Authorization: Bearer <access token>Authorization: Bearer <API key>, no token request or refresh
/{account_id}/messages/submitPOST /emails
senderAddress + headerFromAddress + headerFromNamefrom: "Name <email>"
recipientAddress (one per message)to (string or array); to send many, use POST /emails/batch
subject, html, textsubject, html, text
messageType: EMAILImplied; the endpoint only sends email
attachments: [{ content, contentType, filename, disposition, contentId }]attachments: [{ content (base64), contentType, filename }]
tags (array of strings)tags: [{ name, value }]; for example "welcome" becomes { name: "type", value: "welcome" } (letters, digits, _ and - only)
scheduleAtsend_at (ISO 8601 with an offset)
data (values for templates)variables for a stored template, or render in your code
flowSelectorNo equivalent; Envello has no per-message flow routing
mimedata (complete MIME message)No equivalent; pass the parts as fields

Flows and templates

Flowmailer decides processing and templates in flows you configure in its dashboard, and its documented template engine is FreeMarker. Envello has no flows. Render the HTML in your code and send it as html, or recreate a plain template with {{variable}} placeholders and send template_id with variables.

Authentication

With Flowmailer you request a token, cache it and retry once on a 401. Envello's API key is static and sent as a Bearer token on every call, so the token cache and retry code can be removed.

Hosting

Flowmailer is a Dutch company, so residency alone isn't a reason to move. Weigh the API surface and tooling instead.

Four steps

The migration, end to end

1. Add Envello DNS records alongside your existing Flowmailer records

Verify your sending domain in Envello and add the SPF include, DKIM CNAMEs, and the return-path CNAME Envello generates. Keep your existing records in place: both providers can authenticate the same domain at once, which is what makes a safe cutover possible. Only remove the old records after Envello has been the sole sender for a few days.

2. Swap the sending call

Point your outbound path at Envello's SDK. The request shape (from, to, subject, html, text, cc, bcc, reply_to, headers, attachments) mirrors the common transactional-API pattern, so the diff in most codebases is the import line, the client instantiation, and the API key environment variable. Templates rendered client-side (React Email, MJML, plain string) plug straight into the html field.

3. Dual-send during the cutover window

Route a small percentage of traffic to Envello first, or fork production sends so each message goes through both providers to non-critical recipients while you verify. Envello's log search shows every send, bounce, complaint, open, and click for 90 days on Pro (7 days on Free, up to 365 days on Scale) so you can confirm parity before flipping the rest of the traffic.

4. Cut over and retire Flowmailer

Once Envello has handled a full week of production traffic without regressions on your key deliverability metrics (bounce rate, complaint rate, delivered rate per domain), route 100% of sends through Envello. Export your Flowmailer suppression list and add each address with Envello's POST /suppressions so previously-suppressed recipients stay suppressed. Remove the old DNS records last.

Sending HTML from React components? See the React Email guide for how render() plugs straight into the html field.

FAQ

Migration questions

Can I keep sending through Flowmailer while I test Envello?+

Yes. Both providers authenticate the same domain via separate DKIM selectors and their own SPF include, so parallel sending is safe as long as each provider's records are in place. Keep the old records until Envello has been the sole production sender for a few days, then remove them.

What happens to my suppression list?+

Export it from Flowmailer and add each address with POST /suppressions (a full-access API key works, one address per request), or one by one in the dashboard. If you skip this step, addresses that Flowmailer had marked as bounced or complained can send successfully through Envello on day one and generate the same bounce or complaint again, which harms deliverability. Import first, cut over second.

Do I need to change my webhook consumer?+

Yes, at least the payload shape. Envello's webhooks send delivered, bounced, complained, opened, and clicked events with HMAC-signed payloads; the field names and signature header are documented at envello.dev/docs. If your current consumer branches on your existing provider's specific bounce-subtype taxonomy, decide upfront how each subtype maps to Envello's simpler event set before writing the new handler.

How long does the whole migration take?+

For a codebase with a single central sending path, most teams complete the code change in under an hour. Add DNS propagation (up to 48 hours, usually much less), a dual-send verification window (a few days), and one week of production monitoring before retiring the old provider. Plan for two to three weeks end-to-end, not one afternoon.

Free tool

Check your own GDPR/DPA gaps before you switch

8 questions covering data residency, retention, and subprocessor documentation, the same things a security questionnaire asks.

Run the free checklist →
Ready to migrate?

Start free and migrate at your own pace.