Connect Your Cloudflare Account
The first wizard step connects your Cloudflare account so FlareWatch can deploy workers and KV namespaces. There is no API token to create and no Account ID to find. You authorize FlareWatch once on a Cloudflare consent screen.
Connect Cloudflare
Click Connect Cloudflare
Review and approve
Cloudflare shows the access FlareWatch is requesting. Approve to continue.
Pick an account (if asked)
If your authorization covers more than one account, the wizard shows an account picker. Choose the account to deploy to. If only one account is available, it is selected automatically.
What you grant
Approving the consent screen lets FlareWatch:
- read and update Workers scripts,
- read, create, and write Workers KV,
- read your account name and workers.dev settings,
- read zones and create/update DNS records for automatic custom-domain setup.
DNS access is used only if you choose automatic custom-domain DNS.
License and account binding
Your license can be linked to one Cloudflare account at a time. If it is already linked to a different account, the wizard stops after account selection and tells you which account holds it.
To move the license, delete the current deployment first. Redeploying to the same account reuses the existing link.
How access is stored
FlareWatch stores only an encrypted refresh token (AES-256-GCM), never a long-lived API token. The access token used for deploys is short-lived and never reaches your browser.
Access refreshes automatically for redeploys, so you don't re-consent each time you update. You can revoke access any time from your Cloudflare dashboard, or with Disconnect in the wizard. See Security & Trust Model for details.
Next: Configure monitors.