Skip to main content
Cloudflare hosts DNS for many MSPs’ clients, proxies and protects their websites, and runs their Zero Trust access: Access applications, Gateway filtering, WARP devices and Cloudflare Tunnel. Connect it, and Neo agents can check a domain’s mail records and add the ones a service needs, tell whether a website is proxied and how its SSL is set, and find which policy, rule or tunnel stops a user.

What Neo can do with Cloudflare

  • DNS: read, add, change and remove records, and see which are proxied
  • Email deliverability: check SPF, DKIM, DMARC and MX, and add the records a mail service such as Mailchimp or Microsoft 365 asks for
  • Websites: read zone settings such as the SSL mode, certificates and cache rules, and purge the cache
  • Zero Trust: read Access applications and policies, the Access login log, Gateway rules and WARP devices
  • Tunnels: check each Cloudflare Tunnel’s status, its connectors and the hostnames and networks it serves
  • More: WAF and security rules, load balancers, email routing, Workers and Pages, analytics and the audit log
See Cloudflare API for the permission groups.

Your accounts and zones are mapped to your PSA companies

MSPs hold clients in Cloudflare in two ways: an account for each client, or one account with every client’s zones (a zone is one domain). Neo maps both on the Cloudflare card’s Organization Mapping tab, refreshed on each PSA metadata sync:
  • An account is matched to the PSA company with the same name. Only an exact match to one company is used as it is; every other match is a suggestion.
  • A zone is matched to the PSA company whose website is that domain, and suggested by AI for the rest. These matches are suggestions.
  • When you map an account to a company by hand, each zone in that account follows it at the next sync, except a zone whose domain is a PSA company’s website: that zone keeps its website match as a suggestion, so confirm it on the tab.
  • If the account also holds another company’s zone (its domain is that company’s website, or you mapped it to that company), Neo treats it as your shared account, and its other zones follow no one. In a shared account, map each zone by hand, not the account.
Confirm the suggestions on the Organization Mapping tab, or set the right company by hand, before agents use them on a ticket. A mapping you set by hand survives every later sync. On a ticket, an agent works in Cloudflare only on the accounts and zones mapped to the ticket’s company, and can list the zones of a mapped account. Lists of everything your token reaches are read from a scheduled agent or a chat. A client that keeps its own Cloudflare account can get its own token on the card (Add a customer’s own key). That token reaches only the accounts and zones mapped to that client, so map them on the tab first.

Next steps

Connect Cloudflare

Create a Cloudflare API token and save it in Neo.