Integrations
Cloudflare logo

Cloudflare integration

Developer Tools & Infrastructure · 13 actions · API key auth

Cloudflare DNS, WAF, zones, firewall rules, and load balancer management.

Overview

The ModuleX Cloudflare integration lets a ModuleX agent operate Cloudflare on your behalf — running create, update and remove actions across zones, dns records and waf lists — directly from a plain-English request, using your organization's own Cloudflare credentials. No pre-built workflow is required: the agent picks the right Cloudflare action for the task.

Cloudflare is a developer tools & infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Cloudflare action — or, when you want a repeatable process, the composer assembles a Cloudflare workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Cloudflare in plain English

Type what you want. A ModuleX agent picks the right Cloudflare action — or chains several — and runs it. No workflow to build.

  • Create a new DNS record within a specific zone
    resolves tocreate_dns_record
  • Find the waf list I describe and update it
    resolves tolist_waf_listsupdate_waf_list
  • Update an existing DNS record
    resolves toupdate_dns_record
  • Show me the zones that match what I describe
    resolves tolist_zones
Use cases

What you can automate with Cloudflare

  • Find the right waf list and update it in one promptlist_waf_listsupdate_waf_list
  • Pull a list of zones for a reportlist_zones
  • Create a dns record straight from a requestcreate_dns_record
At a glance

Cloudflare integration at a glance

CategoryDeveloper Tools & Infrastructure
Actions available13
AuthenticationAPI key
Uses your own credentialsYes
Works with the assistantYes
Works in the composerYes
Multi-step / tool-chainingYes
Technical referenceView docs
Integration version1.0.0
Last updatedJun 2026
Reference

All 13 Cloudflare actions

Zones1
list_zones
List, search, sort, and filter your Cloudflare zones
Dns Records3
create_dns_record
Create a new DNS record within a specific zone
update_dns_record
Update an existing DNS record. Only provided fields are modified.
delete_dns_record
Delete a DNS record within a specific zone
Waf Lists4
list_waf_lists
Fetch all WAF lists (no items) for an account
create_waf_list
Create a new empty WAF list for the account
update_waf_list
Update the description of a WAF list (cannot update items)
delete_waf_list
Delete a WAF list
Accounts1
list_accounts
List all accounts accessible to the user
Account Members1
list_account_members
List members of a given Cloudflare account
Firewall Rules1
list_firewall_rules
List firewall rules for a specific zone
Monitors1
list_monitors
List all load-balancer monitors in a Cloudflare account
Pools1
list_pools
List all load balancer pools in a Cloudflare account

See full parameters and response schemas in the Cloudflare integration docs

Two ways

Two ways to use Cloudflare in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Cloudflare action and runs it — no workflow to build.
Compose a workflowNeed it to happen every time? Describe the process and the composer wires Cloudflare into a repeatable workflow you can run on a schedule, from chat, or as an API.
Security

Connecting Cloudflare

API keyCloudflare uses API-key authentication. You provide your own Cloudflare secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Cloudflare without re-authenticating.

Step-by-step setup in the Cloudflare docs

Related

Pairs well with Cloudflare

Agents often chain Cloudflare with these — connect them once and the agent can use all of them in a single task.

FAQ

Cloudflare + ModuleX FAQ

A ModuleX agent can run any of Cloudflare's 13 actions — across zones, dns records, waf lists and accounts — from a plain-English request, using your organization's own Cloudflare credentials.
No. The agent selects the right Cloudflare action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.
Via your own Cloudflare API key, stored encrypted and scoped to your organization.
13, spanning zones, dns records, waf lists and accounts.
Cloudflare runs on your own credentials, so any Cloudflare usage is billed by Cloudflare directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Cloudflare to work in ModuleX.

Connect Cloudflare once with your own credentials and let your agent run all 13 actions on demand.

Last updated: Jun 2026Browse all 175 integrations →