Cloudflare® Workers Bindings & Environment Variables

This document provides a comprehensive reference for all bindings, environment variables, and secrets used in the Cloudflare® Workers project.

Table of Contents

• Secrets & Environment Variables
• Service Bindings
• KV Namespace Bindings
• R2 Bucket Bindings
• D1 Database Bindings
• AI Bindings
• Vectorize Bindings
• Browser Bindings

Secrets & Environment Variables

Service Bindings

KV Namespace Bindings

R2 Bucket Bindings

D1 Database Bindings

AI Bindings

Vectorize Bindings

Analytics Engine Bindings

Browser Rendering

Report-worker uses the Cloudflare Browser Rendering REST API (no wrangler binding needed):

POST https://api.cloudflare.com/client/v4/accounts/{id}/browser-rendering/pdf
Authorization: Bearer {CF_API_TOKEN}
Body: { html: "...", options: { format: "A4" } }

Local Development URLs

For local development with wrangler dev, the following service URLs are used:

Configuration

Each worker contains a .dev.vars file for local development which should be populated with the appropriate values. These files should not be committed to the repository.

Example setup for .dev.vars files can be found in the corresponding .dev.vars.example files in each worker directory.

Setting Up Secrets

For production deployment, secrets should be set using the Wrangler CLI:

wrangler secret put SECRET_NAME

This will securely store the secret and make it available to the worker at runtime.

Cloudflare® and the Cloudflare logo are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions.