How to Connect Your Own Cloudflare Account to CallPages (Infra Tab)
Learn · Infrastructure · Last updated October 13, 2026
What this does and why it matters
Every CallPages business runs on infrastructure — workers that serve your pages, databases that store your bookings, keys that power translations. By default, all of that runs on CallPages' shared account. On October 13, 2026, our shared free-tier usage hit the ceilings (D1 writes: 108,410 of 100,000/day; worker invocations: 80,240 of 100,000/day) — real growth, and the moment we shipped the architectural answer.
By connecting your own Cloudflare account in the 🏗️ Infra tab, you get:
- Your own request quota — your pages and calls draw on your Cloudflare limits, not the shared pool
- Your own database writes — your bookings never compete with another business's background work
- Your own API keys — add your Gemini, OpenAI, and image-generation keys per business
A busy neighbor can never starve your calls.
Step 1 — Open the Infra tab
- Sign in to your owner dashboard at callpages.me/dashboard.
- Click 🏗️ Infra (the Infrastructure tab,
/settings/infrastructure).
The Cloudflare connection area of the Infra tab.
Step 2 — Start the Cloudflare connection
- In the ☁️ Cloudflare card, click the Open Cloudflare button (the magic-token link).
- Cloudflare opens on its token-creation page with two things already filled in:
- Token name:
CallPages {your name} - Exactly 4 permissions, pre-selected:
- Workers Scripts — Edit
- Workers KV Storage — Edit
- D1 — Edit
- Account Settings — Read
- Check the summary screen shows those four permissions, then click Create Token.
- Cloudflare shows you the token once. Copy it.
Tip: You can create a user token (profile → API tokens) or an account token (dashboard → API tokens) — both work. The wizard verifies each through the proper Cloudflare endpoint. This full flow was verified end to end on a real Cloudflare account (account-owned token) on October 13, 2026 — all probe steps passed.
Step 3 — Paste the token and verify
- Back in the Infra tab, paste the token into Código de conexión (connection code).
- Press Conectar (Connect).
- CallPages runs an automatic probe that checks the token and each permission individually: it creates tiny throwaway resources — a probe worker script, a probe database, a probe KV namespace — verifies they work, and deletes them again.
- Nothing is stored until everything verifies. If a permission is missing, the wizard tells you exactly which one; edit the token in Cloudflare (its value doesn't change), press Connect again.
When all steps are green, your connection status reads connected — your business is now on its own Cloudflare infrastructure.
Step 4 — Add your own API keys (optional but recommended)
In the same Infra tab, scroll to the key cards:
Gemini, OpenAI, image generation, and your Google connection status.
- 💎 Gemini: paste your key once. Your page translations automatically use your key first (falling back to the central key only when unconnected).
- 🤖 OpenAI (ChatGPT): key is the only connection route; usage draws on your quota.
- 🖼️ Creación de imágenes: your image-generation key; without it, the Gemini card key or a shared key is used.
- 🔍 Google: shows your Gmail-linked account with Connect/Disconnect.
Good to know: disconnecting a provider deletes the stored key/token copy — addresses and links never change, and nothing else is affected.
Understanding priority levels (first gates live now)
Behind the scenes, CallPages is rolling out explicit priority levels so tight capacity never threatens what matters most — and the first gates are live as of October 13, 2026:
| Level | Workload | Behavior under pressure |
|---|---|---|
| 0 — Always | Live calls, your public page, saving a booking | Never shed, never queued behind background work |
| 1 — High | Calendar sync, support operations | Protected until extreme pressure |
| 2 — Deferrable | Analytics aggregation, translations | Paused, queued, resumed when capacity returns |
| 3 — Background | Bulk sweeps, sitemap, auto-images | First to pause; queued, never dropped |
What's enforced today: connection open/close analytics events are no longer written to the database, repeat page views collapse per session within a minute, repeated errors log once per 5 minutes instead of once per occurrence, the background translation sweep runs roughly every 25 minutes, and the parity watcher every 6 hours. Shed load is queued, never dropped — these levels are being rolled out now as the design contract for all background workloads.
Troubleshooting
- "The pasted token could not be verified" — create a fresh token in Cloudflare (token values are shown once at creation) and paste the new one. Make sure you copied the token value, not the token name or ID.
- A permission is missing — edit the token in Cloudflare (pencil icon on its row), add the named permission, save, and press Connect again. No re-paste needed; the token value doesn't change when you edit permissions.
- Multiple Cloudflare accounts — if the token can see more than one account, the wizard asks you to pick the Account ID so it connects the right one.