Send Integrations

Instructions

Ask which ESP the user wants to connect. If unsure, share the full list of supported ESPs below.
Determine integration type: API (recommended, simpler setup — only an API key is needed) or SMTP (for self-hosted MTAs or SMTP-only providers — requires host, port, TLS setting, username, and password).
Confirm prerequisites: verified sender domain in EmailElement (Sender Domains) and active account with the chosen ESP.
Create the integration: navigate to Send Integrations > click Create Send Integration > select type (API or SMTP) > choose the ESP from the dropdown > click Next > enter integration name > select verified sender domain(s) > enter credentials > optionally add Custom Headers > click Create.
Verify: click Run Test. Validation shows per domain. At least one domain must succeed for the integration to be active.
Configure optional settings: Volume Caps per domain (per hour or 24 hours), Custom Headers.

These ESPs connect via API key. Select API as the integration type:

ESP	Notes
SendGrid	Requires Mail Send + Event Notifications permissions. See send-integration-sendgrid skill for detailed setup.
Brevo (Sendinblue)	Uses Brevo API key (v3).
Postmark	Uses Server API Token.
AWS SES	Requires Access Key ID + Secret Access Key. Select the correct AWS region. Also available as SMTP.
Mailgun	Uses Mailgun API key. Select US or EU region.
SparkPost	Uses SparkPost API key.
Mailchimp (Mandrill)	Uses Mandrill API key (Mailchimp Transactional).
Elastic Email	Uses Elastic Email API key. Also available as SMTP.
Mailtrap	Uses Mailtrap API key.
Resend	Uses Resend API key.
Mailersend	Uses Mailersend API key.
ExpertSender	Uses ExpertSender API key.
Infobip	Uses Infobip API key + Base URL.
Campaign Refinery	Uses Campaign Refinery API key.
theMarketer	Uses theMarketer API key.
SendX	Uses SendX API key.
Alibaba	Uses Alibaba AccessKey ID + Secret. Requires region selection.
OpenText	Uses OpenText API credentials.
JangoMail	Uses JangoMail API credentials.
Gmail	Uses Gmail OAuth. Also available as SMTP.

These connect via SMTP relay. Select SMTP as the integration type. Requires: host, port, TLS setting, username, and password.

ESP / MTA	Notes
KumoMTA	Self-hosted open-source MTA. Host and port configured per deployment.
PowerMTA	Self-hosted commercial MTA. Host and port configured per deployment.
Inboxroad	SMTP relay service.
Gmail	Also available as API (see above).
SMTP2GO	SMTP relay service.
smtp.com	SMTP relay service.
Elastic Email	Also available as API (see above).
AWS SES	Also available as API (see above).
Generic SMTP	Bring your own SMTP server with automatic bounce tracking. Requires a sender domain whose Mail Exchange (MX) record is validated on the Sender Domain page: the bounce return path is delivered to the sender domain itself, the same way the one-click unsubscribe address is. The sender-domain dropdown only lists domains that qualify.

If the ESP or MTA you need is not listed above, contact support@emailelement.com. We can add new integrations based on customer requests.

Multiple sender domains per integration — one integration can send from multiple identities
Failover — configure multiple integrations; the system auto-rotates and deactivates failing ones
Assign Email Domain Groups — route specific recipient domains (e.g., Google, Yahoo) to specific integrations
Assign Weights — distribute sending across integrations by percentage (must total 100%)
Volume Caps — set per-domain caps (per hour or 24 hours) to control sending rate

For detailed setup guides, load the appropriate reference file: