Connecting Cloudflare to Turtini

Connecting Cloudflare lets your org manage DNS records, zone security, SSL, Page Rules, and domain registration for your public websites — all from inside Turtini. It also powers custom-domain publishing for Builder sites.

You'll need two things from Cloudflare before you start:
• An API token with the right scopes
• Your Cloudflare Account ID

To create the API token:
1. Sign in to Cloudflare and open Profile → API Tokens (dash.cloudflare.com/profile/api-tokens)
2. Click "Create Token" and pick the "Edit zone DNS" template
3. Under Permissions, add a second row: Account → Zone → Edit. This one lives under the Account category (separate from the zone-level permission already in the template) and is what lets Turtini register new domains in the account.
4. Under Zone Resources, pick "Include → All zones" from the account you want Turtini to manage
5. Click "Continue to summary" → "Create Token" and copy the token string shown once on the confirmation screen. Copy the token value itself — not the token's display name from the tokens list.

Your Account ID is on the right-hand "API" panel of any existing domain's Overview page in Cloudflare. You can also read it off the dashboard URL: it's the hex string in dash.cloudflare.com/<accountId>/.

To connect in Turtini:
1. Go to Websites → Domains
2. Click "Connect Cloudflare"
3. Paste the API token and Account ID and click Connect

Only org owners and admins can connect, manage, or disconnect Cloudflare. The API token is stored server-side as a secret — it's never sent back to the browser after the initial save.

Disconnecting Cloudflare removes the stored token and all Turtini-side metadata. Your zones, DNS records, and domains remain untouched in Cloudflare itself.