> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Cloudflare to Neo

> Create a Cloudflare API token, save it in Neo, and turn Cloudflare on per agent

You connect Cloudflare once, at the MSP level, with an API token. A client that keeps its own Cloudflare account can add its own token later.

## 1. Create an API token

**1. Open API Tokens**

In the Cloudflare dashboard, open **Manage Account > Account API Tokens** for a token that belongs to one account, or **My Profile > API Tokens** for a token that reaches every account your user is a member of (one per client, for example).

**2. Create a custom token**

Click **Create Token**, then **Create Custom Token**. Add the permissions your agents need. A good start for tickets about DNS, websites and Zero Trust:

* **Zone > DNS: Edit** (or Read), **Zone > Zone: Read**, **Zone > Zone Settings: Read**, **Zone > SSL and Certificates: Read**
* **Account > Account Settings: Read**, **Account > Cloudflare Tunnel: Read**
* **Account > Access: Apps and Policies: Read**, **Account > Zero Trust: Read**

Under **Account Resources** and **Zone Resources**, pick the accounts and zones Neo may reach. A call outside them is refused by Cloudflare.

**3. Copy it**

Create the token and copy it. Cloudflare shows it once.

Neo does not take the Global API Key: it reaches everything your user can do and cannot be limited.

## 2. Add the token in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Cloudflare card, under Networking.

**2. Save the token**

Paste the **API Token** and click **Save**. Neo checks the token with Cloudflare before saving, so a wrong, expired or disabled token is reported straight away.

Neo then lists your accounts and zones and suggests the PSA company for each on the **Organization Mapping** tab. Confirm them there before agents use them on a ticket.

## 3. Turn Cloudflare on per agent

Open the agent, go to the **Tools & Settings** tab, and configure the Cloudflare block under **Tools & Integrations**. Pick a profile, or set each area:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **DNS** | Disabled, Read Only, Read/Write | Records and proxying. Helpdesk asks a technician before a change. |
| **Zones, Settings & Cache** | Disabled, Read Only, Read/Write | SSL mode and other zone settings, cache purges. Each of these, and deleting a zone, always asks a technician. |
| **SSL/TLS & Certificates** | Disabled, Read Only, Read/Write | Edge, origin and custom certificates. Every change always asks a technician. |
| **Zero Trust Access** | Disabled, Read Only, Read/Write | Access applications and policies. Every change always asks a technician. |
| **Zero Trust Gateway, Devices & DLP** | Disabled, Read Only, Read/Write | Gateway rules and WARP devices. Every change always asks a technician. |
| **Tunnels & Networks** | Disabled, Read Only, Read/Write | Tunnel health and private routes. |
| **Email Routing & Email Security** | Disabled, Read Only, Read/Write | Email routing rules and Email Security. Every change always asks a technician. |
| **Accounts, Members & Billing** | Disabled, Read Only, Read/Write | Members, roles and API tokens. Every change always asks a technician. |

Every Security & WAF change always asks a technician, because one can switch a protection off. The other groups (Load Balancing & Traffic, Workers, Pages & Developer Platform, Analytics, Logs & Notifications, Threat Intelligence & Radar, Domain Registration) work the same way. See [Cloudflare API](https://docs.neoagent.io/agents/tools/networking/cloudflare-api.md) for what the agent can do.

## Set up an agent

Ask your Neo Support Agent for the agent you need, for example: "Add Cloudflare to our website agent, read only: on a ticket about a website or email, check the client's DNS records, whether the website is proxied and its SSL mode, and SPF, DKIM and DMARC, and put what you find in an internal note."


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.