Integrations
Email integrations — the providers that deliver your emails, which one is the default, and whether each one works.
Where: Email → Integrations · /projects/<project>/emails/integrations
An email integration is the provider that delivers your emails: AWS SES, Twilio SendGrid, Mailgun, any SMTP server, or the built-in Fake provider that delivers nothing. The list Email Service Integrations shows every integration of the current environment and which one is the default.

Columns, search and filters
Integration Name
The name; press it to open the integration.
Provider
Fake, SendGrid, MailGun, AwsSes or Smtp.
Sender Email Address
The "from" address, for example no-reply@acme.example.
Sender Display Name
The "from" name, for example Acme.
Enabled
True or False. A disabled integration is never used.
Default
DEFAULT on the integration the campaign form and the trigger actions pre-select (in another environment: DEFAULT FOR TEST, and so on).
When more than one integration is enabled and none of them is the default, the warning No Default Set For Active Integrations appears above the list. The list has no filter.
Inside an integration, badges show its state: DEFAULT, ENABLED / DISABLED, TESTED / NOT TESTED, CONFIRMED / NOT CONFIRMED (someone pressed I received it after a test).
What you can do here
Connect a provider — Add New Integration, then the provider's page
Test an integration — send a real test email, confirm it arrived, check the sender domain
Set as default — the integration new campaigns and triggers pre-select
Disable or delete — stop using it, or remove it
Validation integrations — address-checking services (no screen; API only)
Do it from code
Last updated
Was this helpful?