Technical Brief
Proposal · Wow House Studio

Bulk Webflow Updates at Scale
via Cloudflare Workers

I build CF Workers that interface with Webflow's CMS API to execute precise, high-volume updates across thousands of pages — with full audit logging and zero downtime.

Core Capabilities
⚡

CF Workers at Scale

6+ production Workers deployed. Routing logic, KV storage, rate limiting, bulk operations across large content trees.

🔗

Webflow CMS API

Bulk PATCH/DELETE operations, collection item management, staged rollouts with rollback capability.

🔍

Precision at Scale

Pagination handling, exponential backoff, idempotency keys. No duplicate writes, no missed pages.

📊

Audit & Reporting

Every change logged with timestamp, item ID, old/new value. Delivered as TSV or JSON on completion.

Cloudflare Workers Webflow CMS API KV Storage Rate Limiting Bulk Operations Audit Logging
Sample Worker — Webflow Bulk Field Update
// CF Worker: Bulk-update a custom field across all Webflow course pages
// Handles pagination, rate limits, and audit log → KV

export default {
  async fetch(request, env) {
    const { searchParams } = new URL(request.url);
    const fieldSlug  = searchParams.get('field');
    const newValue   = searchParams.get('value');
    const dryRun     = searchParams.get('dry') === '1';

    const items   = await fetchAllItems(env.WF_TOKEN, env.COLLECTION_ID);
    const log     = [];
    let   updated = 0;

    for (const item of items) {
      if (item.fieldData[fieldSlug] === newValue) continue;

      if (!dryRun) {
        await patchItem(env.WF_TOKEN, item.id, { [fieldSlug]: newValue });
        await sleep(120); // Webflow: 60 req/min rate limit
      }

      log.push({ id: item.id, slug: item.fieldData.slug,
                  old: item.fieldData[fieldSlug], new: newValue });
      updated++;
    }

    await env.AUDIT_KV.put(
      `update-${new Date().toISOString()}`,
      JSON.stringify({ field: fieldSlug, updated, dryRun, log })
    );

    return Response.json({ ok: true, updated, dryRun, sampled: log.slice(0, 5) });
  }
};
Engagement Timeline — 2 Weeks
1

Day 1–2 · Audit & Dry Run

Map all affected collection items. Run Worker in dry-run mode. Confirm scope, field names, and edge cases before touching production.

2

Day 3–8 · Staged Rollout

Execute updates in batches of 500. Verify each batch against audit log before proceeding. Slack/email updates every 500 items.

3

Day 9–10 · QA & Verification

Spot-check 50 random pages. Cross-reference Webflow CMS vs audit log. Document any exceptions.

4

Day 11–14 · Handoff

Deliver final audit TSV, Worker source, and KV export. CF Worker stays deployed and reusable for future bulk operations.