v1.13.0Website
•2 min read

Cloudflare Workers Integration

Connect Cloudflare and keep a Worker's secrets, Previews secrets and build variables in step with your project's keys, with the same previews, retries and strict ownership as Vercel and Supabase.

#What's Changed

  • [Feature] Connect Cloudflare from a project's Integrations page and approve one or more accounts. Owners and admins link Workers; other members see their status.
  • [Feature] Map each environment to a Worker's Production secrets, Previews secrets, or Workers Builds variables for production and preview builds. Targets a Worker doesn't offer are greyed out with the reason, and build targets are never ticked for you.
  • [Feature] Syncs run when keys change, on the retry sweep, and from Sync now with a preview of every change. Production changes are batched, so a sync usually deploys a single new Worker version, and they are applied last.
  • [Feature] ApiVault only changes the secrets it created on each target. A secret, variable or binding you added with the same name is reported as a conflict for that target only, and values over 5 KiB are skipped.
  • [Improvement] Unlinking deletes what ApiVault created on every target, and disconnecting hands back that project's Cloudflare tokens without affecting other projects connected with the same login. Remove anyway lists anything left behind.
  • [Improvement] Audit logs, the Integration filter (?integration=cloudflare) and log exports name Cloudflare, the account and Worker, and how many Worker versions a sync deployed.
  • [Improvement] The retry sweep takes turns across Vercel, Supabase and Cloudflare, so a busy provider can't hold up the others.