Integrations

Every integration receives a customer Runtime URL and a revocable sending-only key. It does not receive access to your CFsend account or Cloudflare account. Node.js, Strapi, Shopify and n8n packages are available from npm; adapters without a public registry or marketplace release remain labeled Source preview.

Supported connection paths

• WordPress/WooCommerce plugin routes wp_mail, core and store notifications.
• Node.js/Next.js uses @all2cf/send; PHP uses all2cf/send.
• Laravel, Django and Strapi use product adapters backed by the public Send API.
• Shopify uses the connected app bridge; Shopify-owned platform notifications cannot be globally replaced.
• Auth0 uses a Custom Email Provider Action; n8n uses n8n-nodes-all2cf-send.
• MCP gives AI tools scoped access; signed Webhooks deliver events to applications.

Create a separate key for each application and environment so it can be rotated or revoked independently.

Setup pattern

1. Deploy and verify the Runtime.
2. Create a sending-only key named for the integration and environment.
3. Configure ALL2CF_SEND_URL and ALL2CF_SEND_KEY (or the adapter’s credential fields).
4. Send a verified test and find its message ID in Emails.
5. Enable production recipients only after domain and delivery checks pass.

An Available integration still needs its package/adapter installed in the target application. A Source preview has passed repository contracts but is not yet a supported registry installation. CFsend does not need administrator access to that application after configuration.