Integration

Cloudflare integrations on Wodby

Use Cloudflare across several Wodby workflows: send transactional email through Cloudflare Email Service, connect application code to Cloudflare APIs, protect forms with Turnstile, send backup archives to R2, or place app endpoints behind Cloudflare Access or enrolled Cloudflare One devices. Each selected kind exposes only its own credentials and configuration.

VariablesVariablesApplication AccessStorageSMTP

Send email through Cloudflare Email Service

Relay transactional email from OpenSMTPD with an Email Sending API token for an onboarded Cloudflare sending domain.

Send backup archives to R2

Use an Account ID and R2 API token access key pair to select Cloudflare R2 buckets for automatic backup archives.

Connect apps and protect endpoints

Attach scoped API credentials or Turnstile keys to services, and publish app endpoints behind Cloudflare Access or Cloudflare One.

Supported workflows

How Cloudflare fits into Wodby

Application Access connects Cloudflare to the app itself. Other supported integration kinds remain separate workflows for provider variables or network services where available.

Variables

API

Inject Cloudflare 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

CLOUDFLARE_ACCOUNT_IDCLOUDFLARE_API_TOKEN
See integration workflows

Variables

Turnstile

Inject Cloudflare 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

TURNSTILE_SITE_KEYTURNSTILE_SECRET_KEY
See integration workflows

Application Access

Application Access

Publish Wodby apps behind Cloudflare Access or route private endpoints to enrolled Cloudflare One devices.

  • Choose protected publishing with an identity policy or private-network access for enrolled Cloudflare One devices.
  • Protect every eligible HTTP endpoint or select only the services that should move behind Cloudflare.
  • Wodby manages the Tunnel connection, provider routes, matching public-route suppression, reconciliation, and cleanup.

Configuration surfaced to workloads

Account IDAPI Token
Explore Application Access

Storage

R2

Send backup archives and storage-backed data from Wodby services to Cloudflare R2.

  • A practical fit for stateful services that should keep backup archives outside the running environment.
  • Works with automatic backup workflows and restore paths.
  • Lets teams standardize on an object storage target without changing the app stack itself.

Configuration surfaced to workloads

Account IDAccess Key IDSecret Access Key
See backups and imports

SMTP

SMTP (Beta)

Relay outbound email from OpenSMTPD through Cloudflare Email Service with an Email Sending API token.

  • Onboard the sending domain in Cloudflare Email Service before connecting it to Wodby.
  • Use a Cloudflare API token with Email Sending: Edit permission for SMTP authentication.
  • OpenSMTPD relays through Cloudflare Email Service with implicit TLS on port 465.

Configuration surfaced to workloads

Email Sending API Token
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 Cloudflare.

See integration workflows

Store provider keys, tokens, and DSNs once, then reuse them across environments.

View page

Explore Application Access

Compare public delivery, identity-protected publishing, and private-network access for Wodby apps.

View page

See backups and imports

Use storage integrations as backup targets for stateful services and app data.

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 Cloudflare

Application Access is selected for an app rather than built into its stack. These web stacks are common fits for Cloudflare when the complete app or selected HTTP endpoints should be protected.

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

    OpenSMTPD can relay transactional email through Cloudflare Email Service with the provider integration handling its upstream credentials.

    View stack

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

    Drupal can run behind Cloudflare Access while its database and file backups use R2 as an external destination.

    View stack

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

    WordPress can combine protected preview environments with off-platform backup archives in Cloudflare R2.

    View stack

  • Self-hosted PostgreSQL database stack for applications that want a managed Postgres service inside the same delivery workflow.

    PostgreSQL is a representative stateful service whose automatic backups can be stored in Cloudflare R2.

    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 integrationsApplication Access overview