Connect Cloudflare Email Routing to Your AI Agent

Choose a zone and account for a forwarding map, or provide an exact recipient and verified destination for a new rule. AI can explain the configuration and apply your specified routing choice.

5 tools OAuth / Custom credential

Connect Cloudflare Email Routing Install OOMOL

Try a Cloudflare Email Routing Task

Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.

oo Skill Cloudflare Email Routing

Explain Existing Forwarding Rules

Read zone rules and destination addresses to map matching recipients to their actions and verification state.

/oo Cloudflare Email Routing: Read Cloudflare Email Routing rules for zone [zone ID] and destination addresses for account [account ID]. Summarize matching addresses, forwarding actions, priorities, and destination verification status.

Create an Exact-Address Forwarding Rule

Check destination verification and create the explicit rule you provide.

/oo Cloudflare Email Routing: Check Cloudflare Email Routing account [account ID] destination [destination email] is verified. If verified, create enabled rule [rule name] in zone [zone ID] matching only recipient [custom email address], forwarding to [destination email], priority [priority].

Start Working with Cloudflare Email Routing

Install OOMOL

Set up oo CLI and the oo Skill in your agent.
Install OOMOL →
Connect Cloudflare Email Routing

Authorize Cloudflare through OAuth or connect with supported Cloudflare credentials.
Connect Cloudflare Email Routing →
Give Your Agent a Task

Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →

Choose Your Agent

Codex Claude Code Cursor Hermes

Access to the account and zone with the needed Email Routing permissions.
For credentials, use a cfut_ User API Token or a Global API Key with the account email, plus Account ID and Zone ID.
Account-owned API tokens are not accepted. Forwarding destinations must already be verified.

Cloudflare Email Routing Tools

Cloudflare Email Routing rules connect recipient matches with forwarding, dropping, or Worker actions. Destination verification determines whether an address is ready for forwarding.

Read Rules and Verified Destinations

List zone or account routing rules and filter destination addresses by verification state.

Create or Replace Routing Rules

Create or replace rules with recipient matchers and forward, drop, or Worker actions.

5 tools

List Routing Rules

List Cloudflare Email Routing rules for a zone or account.

cloudflare_email_routing.list_routing_rules

Create Routing Rule

Create a Cloudflare Email Routing rule in a zone. Forward actions require verified destination addresses.

cloudflare_email_routing.create_routing_rule

Update Routing Rule

Replace a Cloudflare Email Routing rule in a zone.

cloudflare_email_routing.update_routing_rule

Delete Routing Rule

Delete a Cloudflare Email Routing rule from a zone.

cloudflare_email_routing.delete_routing_rule

List Destination Addresses

List Cloudflare Email Routing destination addresses and their verification status.

cloudflare_email_routing.list_destination_addresses

Frequently Asked Questions

Can AI explain where each custom address forwards?

Yes. Read the rules and destinations and ask for a table of matchers, actions, priorities, and verification states.

Can this verify a new destination address?

It can read verification state, but these operations do not create or verify destination addresses. Verify the destination before creating a forwarding rule.

Does updating a rule preserve unspecified matchers?

Updating replaces the rule’s matchers and actions. Read the existing rule and provide the full intended matcher and action set.

Can AI read the emails delivered through these rules?

No. This connection manages routing configuration and destination records, not mailbox contents.