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

Integrations

Email delivery providers — SMTP, AWS SES, SendGrid, Mailgun.

Where: Email → Integrations · /projects/<project>/emails/integrations

An email integration is the delivery provider that actually sends your messages — SMTP, AWS SES (Amazon Simple Email Service), Twilio SendGrid, Mailgun, or the sandbox Fake Email (Test Me) provider for testing without real delivery.

Email → Integrations.

What you can do here

Add a provider with its credentials, test it, set one as default, enable or disable providers. Creating an integration does not send anything by itself — it makes the provider available to templates, campaigns, and triggers. Editing a saved integration also shows a domain health panel that checks the DKIM, SPF and DMARC DNS records of your sender domain.

Example: connecting Twilio SendGrid

Pick the provider, name the integration, and fill its credentials — for SendGrid that is the API key and the verified sender:

The New integration form, filled.

After Save the integration appears with its full action set — Set as default, Disable, Test, links to the provider's documentation and to the SDK/API docs, and Delete:

The saved integration and its actions.

Test sends a real probe through the provider — run it once after saving to confirm the credentials work before any template or campaign relies on this integration.

Use it from code

Notifications → Email.

API reference

Endpoints: Get Email Integrations, Save Email Integration, Test Email Integration, Check Email Integration Domain Health.

Last updated