Connect Cloudflare
If Cloudflare sits in front of your app, plenty of incidents start there — DNS, caching, a Worker, a tunnel. Connect it to Microtica Agents so the Investigator can check the edge instead of guessing. The connection is a single Cloudflare API token, verified with Cloudflare and stored encrypted on this project.
Connect
- In your Cloudflare dashboard, create an API token with the permissions you want the Investigator to have. Access follows the token exactly — a narrowly scoped token means narrowly scoped access.
- In the console, open your project’s settings and choose Integrations under Connections.
- In the Edge & infrastructure section, find Cloudflare and click Connect Cloudflare. The Connect Cloudflare dialog opens.
- Paste the token into the API token field and click Connect Cloudflare. Microtica verifies it with Cloudflare before saving; on success the row shows a Connected badge along with the token’s status.
What it unlocks
With a token connected, the Investigator gets Cloudflare tools for DNS, Workers, KV, R2, tunnels, firewall, cache, and edge troubleshooting — always within the limits of the token you created. The token is used only when the Investigator loads Cloudflare tools for this project’s requests.
Disconnect
Click Disconnect on the Cloudflare row. The token is removed from the project. You can also revoke the token in your Cloudflare dashboard at any time — the connection stops working immediately.
If it doesn’t connect
- A Cloudflare connection failed message with “Cloudflare rejected the API token” means the token didn’t pass verification — check that you copied the whole token and that it hasn’t been revoked or expired in Cloudflare.
- The Connect Cloudflare button stays disabled until the token field has content — paste the token itself, not its ID.
That’s the last connection. With your accounts linked, the Investigator has what it needs — time to put it to work.