Choose SMTP relay, API access, or both
Route mail through Brevo from OpenSMTPD, expose provider API credentials directly to application services, or combine both delivery paths.
Integration
Brevo integrations on Wodby
Use Brevo as the SMTP relay behind OpenSMTPD, expose a Brevo API key directly to application services, or enable both kinds from one provider integration. SMTP keys and Brevo API keys remain separate credentials.
SMTPVariables
Keep email credentials reusable
Store provider-managed mail credentials at integration level instead of copying them into application repositories.
Match each kind to its consumer
Attach SMTP settings to the relay service and expose API variables only to application services that need direct provider access.
Supported workflows
How Brevo fits into Wodby
Each supported integration kind maps Brevo into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider configuration into workloads.
SMTP
SMTP
Relay outbound email through Brevo from OpenSMTPD and app workloads.
- OpenSMTPD is the most direct stack-level consumer for SMTP integrations.
- Useful for transactional email flows that should route through a dedicated provider.
- Keeps provider credentials out of the application repository.
Configuration surfaced to workloads
LoginSMTP key
Variables
Variable
Inject Brevo settings into services as environment variables instead of hardcoding them into app code.
- Keep provider credentials, identifiers, and endpoints outside repositories and local dotenv files.
- Attach the integration to reusable stacks, then connect it to the services that actually need it.
- Override values per environment without rebuilding the stack.
Configuration surfaced to workloads
BREVO_API_KEY
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Brevo.
Stack fit
Stacks that commonly pair with Brevo
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
OpenSMTPD
Stack
SMTP server stack that can relay mail directly or integrate with third-party delivery providers for reliable sending.
OpenSMTPD is the most direct stack match when Brevo is the chosen relay provider.
View stackWordPress
Stack
WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.
WordPress projects often need a dedicated transactional email route that stays consistent across environments.
View stackDrupal 11
Stack
Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.
Drupal teams commonly centralize SMTP delivery in the stack rather than configuring it ad hoc per site.
View stackLaravel
Stack
Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.
Laravel apps can keep mail credentials in the integration layer while the app focuses on runtime behavior.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.