More SMTP providers for transactional email

Four new email providers

Mailgun, Postmark, Resend, and SendGrid are now first-class Wodby integrations. Each provider can supply an upstream SMTP relay to OpenSMTPD, API credentials to selected application services, or both. That keeps delivery credentials in reusable integrations instead of duplicating them across app environments.

• MailgunNew providerUse domain-specific SMTP credentials with the US or EU relay for that sending domain, and expose the Mailgun API key and domain when application code needs them.View Mailgun integration →
• PostmarkNew providerUse a Postmark server token for SMTP relay authentication, direct API delivery, or both from the same integration.View Postmark integration →
• ResendNew providerConnect a Resend API key once, then use it through OpenSMTPD or expose it directly to application services.View Resend integration →
• SendGridNew providerUse a SendGrid API key as the SMTP relay password or make it available to services that send through the SendGrid API.View SendGrid integration →
• Cloudflare Email ServiceNew SMTP option · BetaAdd transactional email relay to an existing Cloudflare integration with an onboarded sending domain and an Email Sending API token.View Cloudflare Email Service integration →

Choose SMTP relay, direct API access, or both

The new transactional-email providers support two integration kinds. Choose SMTP when application mail should travel through OpenSMTPD. Choose Variable when application code or a provider SDK should receive the provider's API credentials. Enable both when different services in the same stack use different delivery paths.

Mailgun keeps its SMTP login and password separate from its API key. Postmark, Resend, and SendGrid reuse their provider token or API key for SMTP authentication, so Wodby handles the provider-specific relay details for you.

Cloudflare Email Service joins SMTP

Cloudflare already supports several Wodby workflows. Its integration can now also relay transactional email through the Cloudflare Email Service beta. Before connecting it, onboard the sending domain in Cloudflare and create an API token with Email Sending: Edit permission. OpenSMTPD then uses that token with the service's implicit TLS endpoint on port 465.

See the Cloudflare integration page for its email, backup storage, access, Turnstile, and API options.

One application-facing relay path

With the SMTP kind enabled, applications send mail to OpenSMTPD inside the stack. OpenSMTPD handles the authenticated connection to the selected upstream provider. You can change providers or rotate credentials without putting external relay settings into application code.