Reconcile Email Routing addresses during Worker trigger deployment

Introduced 2026-07-21 · score 0.92

HOW TO USE IT

When a Worker’s Email Routing rules should match its configuration, set top-level `addresses` and run `wrangler deploy` or `wrangler triggers deploy`. Wrangler reconciles managed rules and requires confirmation for destructive changes; non-interactive destructive plans fail after Worker deployment.

npx wrangler deploy

npx wrangler triggers deploy

{
  "name": "<worker-name>",
  "main": "<entrypoint>",
  "compatibility_date": "<YYYY-MM-DD>",
  "addresses": ["<recipient@example.com>", "*@<apex-domain>"]
}

WHY THIS HELPS

Deploy a Worker whose configuration defines Email Routing addresses and keep its routing rules in sync.

REQUIREMENTS AND LIMITATIONS

Version: 4.113.0
addresses: Top-level string array of inbound addresses; each entry is a literal recipient or `*@domain` catch-all. Catch-all supports apex domains only. Omitted means no rule changes; an empty array removes all Email Routing rules managed by this Worker. Ignored under `env`.
Prerequisite: Wrangler 4.113.0 or later.
Prerequisite: For Worker deployment, Wrangler requires at minimum `name`, `main`, and `compatibility_date`; `main` may be omitted for assets-only Workers.
Reconciliation runs after the Worker uploads, or when `wrangler triggers deploy` runs after a version promotion.
Non-interactive destructive plans fail without modifying rules.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

Reconcile Email Routing addresses during Worker trigger deployment