Skip to main content

​
Overview

ElasticFunnels ships its own email engine for broadcasts and automations, but you can also push contacts and send through external platforms when your team already lives there. Every email integration is wired into the automation builder as actions you can drop into any workflow (for example, after a form submission or a purchase).

​
Categories

ESP / contact-sync

Push subscribers, manage tags, and trigger sequences in your existing email service provider.

Transactional email

Send one-off API-driven emails through high-deliverability providers (or any SMTP relay).

Email validation

Verify addresses at form-submit time to keep junk and spam-traps out of your list.

​
ESP / contact sync

Pick where the source of truth lives. If Klaviyo or ActiveCampaign already runs your email program, sync EF data into them. If you want to retire your ESP and run broadcasts from EF, use the built-in Emails module instead.

​
Transactional email

These providers send one-off emails — order receipts, dunning notices, password resets, etc. — through their API or SMTP server. Setup for Amazon SES, Postmark, Brevo and Resend is on Email Sending Accounts, and their opens, clicks and bounces on Delivery events.
The integration shown as Mailrelay in the UI is a general-purpose SMTP integration despite the name — point it at any SMTP server you already operate.

​
Email validation

Both validators plug into:
  • Forms — call the validator inside the automation that runs after the form is submitted, and reject the row if the address is invalid.
  • Automations — gate any subsequent step (add_to_list, tag, send_email) on the validation result.

​
Setup pattern

The setup is the same for every provider:
1

Find the provider

Go to Apps → Integrations, click New integration, and pick the provider under Email Marketing (or Utilities for validation).
2

Authenticate

Paste an API key, OAuth your account, or fill in SMTP credentials depending on the provider.
3

Pick lists / forms (where applicable)

For ESP integrations, the form will load your lists, tags, forms, sequences, etc. directly from the provider so you can choose them by name instead of ID.
4

Use it in automations

Open any Automation and drop the new actions (e.g. Klaviyo: Subscribe Profile) into the workflow. Map ElasticFunnels variables (email, first name, custom fields) to the provider’s fields.

​
The integration page

Mailgun, SendGrid, Amazon SES, Postmark, Brevo and Resend open on a page with the settings in cards and a column beside them:
  • Header: the connection’s name (click it to rename, then Save), its status, when it last sent and its last error. Test connection (SendGrid, Amazon SES, Postmark, Brevo, Resend) checks the saved key. The ⋯ menu opens the email logs or deletes the integration.
  • Connection: the API key and, for Mailgun, the sending domain (the access key and region for Amazon SES, the server token and streams for Postmark). A saved key is never shown again: it reads Saved with a Replace button. Leave it as it is to keep the stored key.
  • Default sender: the from address, from name and reply-to for email sent through this account. How the sender is chosen explains the order, also written out on Email Sending Accounts.
  • Delivery stats (Mailgun, SendGrid) or Delivery events (Amazon SES, Postmark, Brevo, Resend): the webhook that brings opens, clicks and bounces back. See Delivery events.
  • How to set it up (beside the cards, or under them on a phone): the steps with links to the provider.
The Activity tab shows recent sends and failures, Presets offers ready-made automations, and Used by lists the automations and merchants that send through this account.

​
Built-in vs external

ElasticFunnels can replace these tools for many teams. Use the table below to decide: You can also mix-and-match — for example, send transactional through SendGrid and broadcasts through Klaviyo, while EF still owns the funnel data, automations, and reporting.