Cloudflare Setup
Account setup, API tokens, and Wrangler CLI configuration
API Tokens
Create an API token in the Cloudflare dashboard under My Profile > API Tokens.
For Pages and Workers deployment, the token needs:
- Account > Cloudflare Pages > Edit
- Account > Workers Scripts > Edit
- Account > Workers KV Storage > Edit (if using KV)
- Account > Workers R2 Storage > Edit (if using R2)
- Account > D1 > Edit (if using D1)
💡 Tip
Create one token with all permissions rather than separate tokens per service. Store it as CLOUDFLARE_API_TOKEN in your GitHub repo secrets.
Environment Variables for CI
Every project needs these GitHub Actions secrets:
| Secret | Description |
|---|---|
CLOUDFLARE_ACCOUNT_ID | Your Cloudflare account ID (found in dashboard URL) |
CLOUDFLARE_API_TOKEN | API token created above |
IFTTT_PROD_NOTIFY | (Optional) IFTTT webhook URL for deploy notifications |
Wrangler CLI
Wrangler is the Cloudflare CLI. In CI, use npx wrangler@4 to avoid installing it globally. For local development:
pnpm add -D wranglerOr use it via npx:
npx wrangler@4 pages deploy dist --project-name=my-project⚠️ Warning
Always pin to a major version (wrangler@4) to avoid breaking changes. Do not use wrangler@latest in CI.
wrangler.toml
Projects that use Pages Functions, KV, D1, or R2 need a wrangler.toml at the project root:
# Cloudflare Pages project configuration
compatibility_date = "2024-12-01"See Wrangler Config for full details on bindings and configuration.