For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Email Service Integrations list: Test Me (Fake, DEFAULT), SendGrid (example), Mailgun (example), SES (example), Mailpit (local test, Smtp)
Five integrations; the Fake Test Me is the default.

This is the Email version of Integrations. The rules that are the same in every module (environments, the default, integrations in use) are on the Integrations page.

Columns, search and filters

Column
What it shows

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

Do it from code

API: Get Email Integrations · Get Email Integration

Last updated

Was this helpful?