Integration

SendGrid integrations on Wodby

Use SendGrid to relay transactional email through OpenSMTPD, expose a SendGrid API key to application services, or enable both kinds. SMTP relay uses the API key as its password with the fixed username apikey.

SMTPVariables

Choose SMTP relay, API access, or both

Route mail through SendGrid from OpenSMTPD, expose provider API credentials directly to application services, or combine both delivery paths.

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 SendGrid fits into Wodby

Each supported integration kind maps SendGrid into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.

SMTP

SMTP

Relay outbound email through SendGrid 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.
See integration workflows

Variables

Variable

Inject SendGrid settings into services as environment variables instead of hardcoding them into app code.

  • Keep provider keys, tokens, and DSNs 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

SENDGRID_API_KEY
See integration workflows

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 SendGrid.

See integration workflows

Keep SMTP providers reusable across stacks and environments.

View page

Browse all integrations

Compare this provider with the rest of the integration catalog and other supported workflows.

View page

Stack fit

Stacks that commonly pair with SendGrid

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.

  • SMTP server stack that can relay mail directly or integrate with third-party delivery providers for reliable sending.

    OpenSMTPD is the direct relay stack match for any SMTP integration.

    View stack

  • WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.

    WordPress projects often need reliable transactional email routed through a dedicated provider.

    View stack

  • Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.

    Drupal sites commonly centralize outbound email through a stack-managed relay path.

    View stack

  • Laravel

    Stack

    Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.

    Laravel apps benefit from keeping mail credentials attached to the stack instead of the repo.

    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.

Browse all integrationsIntegration feature overview