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
3
Copy it
Create the token and copy it. Cloudflare shows it once.
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.
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:
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 for what the agent can do.
