mailbox-consolidation

Installation
SKILL.md

Mailbox consolidation into one Workspace hub

Self-Evolving Skill: This skill improves through use. If a step is wrong, Google changed behaviour, or a workaround was needed, fix this file immediately. Only record real, reproducible findings, and never add a real address, domain, tenant, rule ID or customer detail: this plugin is public.

The setup: one hub mailbox in a Google Workspace tenant (a shared front-desk inbox) receives everything that used to go to several sources. Each source keeps its own copy. Staff reply from the hub using "send mail as" for each source, so correspondents see no change.

Each source type gets a different mechanism, and each mechanism fails silently in its own way. The rules below were all measured, not taken from documentation.

1. Survey first: read the live state, never the plan

Before changing anything, read each mailbox's actual settings through the Gmail API. Reading needs only gmail.settings.basic or gmail.readonly, and it can be done for consumer accounts too.

GET users/me/settings/autoForwarding        → {"enabled": false} means nothing is forwarded, whatever the docs say
GET users/me/settings/forwardingAddresses   → is the hub even listed, and is it "accepted" or "pending"?
GET users/me/settings/filters               → filters that archive, delete or forward

Then prove where the hub's mail actually came from, using metadata only (no bodies). The Delivered-To chain tells the three routes apart:

Installs
2
GitHub Stars
3
First Seen
Oct 22, 2026