Cloudflare Inbox
Deploy Cloudflare Inbox
Use the Deploy to Cloudflare button, then finish domain and auth setup.
One-click Worker deploy
Use the deploy button from the Cloudflare Inbox landing page:
The deploy flow clones the template into your GitHub/GitLab account, lets you choose project/resource names, builds the Worker, and provisions supported Wrangler resources such as R2 and Queues.
Required deploy inputs
Cloudflare Inbox needs these runtime values:
| Name | Purpose |
|---|---|
AUTH_REQUIRED | Keep production inbox access fail-closed. Use true. |
SUPPORT_ALIAS | Default mailbox fallback, for example support@example.com. |
FORWARDING_ADDRESS | Owner email that receives forwarded messages and magic links. |
INTERNAL_SENDER_EMAIL | Sender used for magic-link emails. |
INTERNAL_SENDER_NAME | Optional display name for internal emails. |
APP_ORIGIN | Deployed app origin, used for absolute download links. |
AUTH_COOKIE_SECRET | Secret used to sign browser sessions and magic-link tokens. |
API_TOKEN | Optional bearer token for machine /api/* routes. |
What remains after deploy
After the Worker is deployed:
- Onboard your domain to Cloudflare Email Service / Email Routing.
- Add the DNS records Cloudflare provides.
- Verify the forwarding destination address.
- Route a custom address or catch-all address to the Worker.
- Open
/login, request a magic link, then open/app. - Send a test inbound email and reply from the web UI.
Local validation commands
Inside the Cloudflare Inbox repo:
npm install
npm run typecheck
npm test
npm run build:worker
npm run dry-run:workerUse npm run deploy or npm run deploy:worker for production deploys once the template scripts are configured.