Cloudflare Service Token

Some resources in MSP environments are protected behind Cloudflare Zero Trust, including internal knowledge bases and operational platforms. To support automation, Neo should be able to authenticate to these resources using Cloudflare Service Tokens as described here: https://developers.cloudflare.com/cloudflare-one/access-controls/service-credentials/service-tokens/

This would use two configuration fields: Service Token ID and Service Token Secret, enabling programmatic access to Cloudflare Access protected resources via Neo’s web fetch capability.

For example, Neo could retrieve a private knowledge base article hosted behind Zero Trust that contains internal troubleshooting steps for Microsoft 365 mail flow issues, then use that context to guide a ticket resolution or suggest remediation steps.

In another example, Neo could access a Hudu instance protected by Cloudflare Access to pull client-specific documentation such as DNS records, VPN configuration details, or credential notes during onboarding or incident response. This would allow Neo to cross-reference live ticket data with authoritative system documentation without requiring a technician to manually log into the platform.

This capability should also extend beyond web pages to include APIs and other services protected by Cloudflare Access. It would allow Neo to interact with secured systems in a consistent, non-interactive way while still respecting Zero Trust access controls and policies.