Use Cloudflare with NimbleBrain.
Connect Cloudflare and just ask — no workflow to build. DNS, Workers, R2 storage, and account bindings. The agent gets 14 actions, running under your own credentials.
Everything the agent can do in Cloudflare
DNS, Workers, R2 and the account bindings underneath them. Useful when the answer to “why is this hostname doing that” is three records deep and nobody wants to open the dashboard.
14 actions
- Create dns record
- Update dns record
- Delete dns record
- List zones
- Create zone
- Update zone
- Delete zone
- List accounts
- List account members
- List firewall rules
- Get lists
- Create list
- Update list
- List monitors
Nobody types an action name
You ask. The agent works out which of its actions that takes, and in what order.
What DNS records point at this hostname?
Calling 3 actions in Cloudflare
- Create dns record
- Update dns record
- Delete dns record
- Working
Which Workers are deployed on this account?
Calling 2 actions in Cloudflare
- List accounts
- List account members
- Working
Check whether this domain is proxied.
Calling 3 actions in Cloudflare
- Create dns record
- Update dns record
- Delete dns record
- Working
Three steps, and Cloudflare is reachable.
-
Install it
Find Cloudflare in the directory inside your workspace and install it. No adapter for us to build first, no queue to join.
-
Connect the account
Sign in at the vendor, or hand an admin credential over once. Tokens stay with the workspace or the person who owns them — never pooled, never copied to us.
-
Ask for the work
The tools show up in front of the agent, under the same access wall as everything else. Describe the job in plain language, or put it on a schedule.
