This profile sends mail using the Cloudflare Email Service REST API. Cloudflare requires a sending domain onboarded for Email Service. The connection needs the Cloudflare account ID and an API token.
Before you begin#
Have a provider account and credentials for the transport you chose. Copy credentials from the provider’s own console or account settings; never put secret values in documentation. Check the provider’s documentation for account requirements and sender acceptance.
Supported transport and settings#
- Transport scheme: cloudflare+api.
- Required settings: Cloudflare account ID (text) and Cloudflare API token (secret).
- Optional settings: There are no additional provider configuration fields for this profile.
Jooosi Mail marks password, token, key, and private-key fields as secrets in the connection form. Enter only the fields shown for the selected scheme.
Create the connection#
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select Cloudflare Email Service in Profile.
- Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
- Review the sender, routing, and advanced settings for this connection.
- Choose Create connection to save it.
For the shared form workflow, see Connect a provider.
Verify delivery#
Follow Send a test email and send to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status.
Webhooks#
This profile does not declare provider webhooks. Review delivery attempts in Jooosi Mail email logs.
Troubleshooting#
- Verify that the sending domain is onboarded with Cloudflare Email Service and that the account ID matches the token.
- If the connection saves but a test fails, inspect its Jooosi Mail log and check the API token permissions with Cloudflare’s documentation.
Provider reference: https://developers.cloudflare.com/email-service/api/send-emails/rest-api/.