Gmail connector should support multiple named accounts

Open 💬 5 comments Opened Jun 28, 2026 by zqchris

Feature request: allow the Gmail connector to connect and target multiple Google accounts at the same time.

Current behavior: the assistant appears to access only one active Gmail account. This makes email-agent workflows incomplete when a user has more than one inbox.

Expected behavior:

Support multiple connected Gmail accounts.
Give each account a stable alias.
Let prompts and tool calls target a specific account or an explicit set of accounts.
Show the source account in search results, summaries, task extraction, and action confirmations.
Default replies and drafts to the original receiving account.
Let automations monitor selected accounts without duplicate alerts.
Fail closed when the requested account is ambiguous.

This is needed for reliable multi-inbox email-agent workflows.

View original on GitHub ↗

5 Comments

rigevo · 1 month ago

I have the same requirement, with a concrete hosted-automation use case.

I need one Codex/ChatGPT user or workspace to connect several independent Gmail accounts, for example Personal, Work, and Project, while keeping every mailbox separate. The current OpenAI-maintained Gmail connector is useful, but its tools bind to the current authenticated Gmail user and do not expose an account_id or connection_id.

The important part is that this must remain an OpenAI-hosted connector experience so delegated tasks and automations can run while the user's computer is turned off. A local MCP workaround does not solve that requirement.

A safe first-class implementation should provide:

multiple named Gmail connections per OpenAI user/workspace;
a separate Google OAuth grant and revocation flow for each Gmail account;
stable connection_id / account labels shown in every result;
per-account permissions such as read-only, drafts, and send;
an explicit, required account selector for every Gmail tool;
no default/fallback account for writes;
read-only cross-account search only when explicitly requested;
draft-first sending with a full preview and explicit confirmation;
fail-closed behavior when an account is missing or ambiguous;
agent/task-level restrictions so a delegated task can be limited to one Gmail connection.

This is not a request to merge or forward all mail into one inbox. Each Gmail account must remain technically isolated, and a message/thread ID from one account must never resolve under another account.

The desired UX is the same as the existing OpenAI Gmail plugin: click “Add Gmail account” again, complete Google OAuth for another mailbox, assign a label, and then choose that named connection in Codex tools and automations.

Antera · 1 month ago

It has been too long, ChatGPT is not usable if it can access only 1 Gmail account, OpenAI please update

erensunerr · 24 days ago

Any update on this?

Antera · 24 days ago

Any update on this?

elix1er · 19 days ago

+1 with a concrete reproduction from ChatGPT Gmail today.

I have two Gmail addresses that I want to use within one assistant workflow. I created separate test drafts targeting each address and then read the drafts back. In both cases the connector created the draft from the same authenticated Gmail account. There is currently no sender/account selector exposed by create_draft.

This matters especially for workflows where identity is part of correctness, such as job applications, client communication, support inboxes, or personal/work separation. A draft that looks correct in the body but originates from the wrong mailbox is a dangerous failure mode.

Strongly support:

multiple named Gmail accounts simultaneously;
explicit account selection on every Gmail tool action;
account/source shown in results and confirmations;
replies/drafts inheriting the original mailbox automatically;
failing closed when multiple accounts are connected but the requested sender is ambiguous.

I would also love cross-account search only when explicitly requested, rather than silently merging inboxes.