App Logo
mail.google.com

Forward Gmail thread

Automatically forward Gmail thread on mail.google.com. Forward an entire Gmail thread to one recipient, with an optional note placed above the forwarded content. Takes the hex threadId that search_emails returns and forwards the whole conversation inline rather than a single message. Returns forwarded, threadId and to once Gmail has accepted the send. A thread id Gmail cannot open is refused with nothing sent, and so is a conversation that still has a scheduled reply pending (Gmail hides its Forward control then). Forwarding a conversation that sits in the Bin works, but Gmail then keeps the sent copy out of the Sent folder.

Input

to required

Recipient email address.

threadId required

Hex legacy thread id.

note optional

Optional plain-text note prepended above the forwarded content.

account optional

Google account email to act as (authuser=). Without it Gmail picks u/0, nondeterministic in a multi-account browser jar.

Output

to required
threadId required
forwarded required

FAQ

Forward an entire Gmail thread to one recipient, with an optional note placed above the forwarded content. Takes the hex threadId that search_emails returns and forwards the whole conversation inline rather than a single message. Returns forwarded, threadId and to once Gmail has accepted the send. A thread id Gmail cannot open is refused with nothing sent, and so is a conversation that still has a scheduled reply pending (Gmail hides its Forward control then). Forwarding a conversation that sits in the Bin works, but Gmail then keeps the sent copy out of the Sent folder.
Ask an AI agent connected to Reduck to run reduck/mail.google.com/forward_email, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/mail.google.com/forward_email
You do not need one. "Forward Gmail thread" drives the real mail.google.com pages in a browser, so it works whether or not mail.google.com offers an API for this.
Required: threadId, to. Optional: note, account.
It returns to, threadId, forwarded.
Yes. It acts as you on mail.google.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the mail.google.com cookies saved by the Reduck extension.
It makes changes on mail.google.com, like sending, posting, booking or buying something.
Ask an AI agent connected to Reduck to run reduck/mail.google.com/forward_email, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/mail.google.com/forward_email
It is part of Reduck's official curated catalogue.

Related scripts

mail.google.com

Search Gmail

Search the signed-in Gmail with the native query syntax (from:, to:, subject:, has:attachment, after:/before:, labels…) and return matching threads: threadId (feed it to get_thread / reply_to_email), sender, senderEmail, subject, snippet, date, unread, starred, hasAttachment. Results are threads rather than individual messages, which is Gmail's own search granularity, and only the first page of results is returned (up to 50).

mail.google.com

Send Gmail email

Send an email from the signed-in Gmail account, with a plain-text body and an optional single file attachment. Always starts a new conversation. To answer inside an existing thread, use mail.google.com/reply_to_email.

mail.google.com

Get Gmail thread

Read a Gmail thread by its hex threadId (as returned by search_emails): subject plus every rendered message's from, fromEmail, to, date, plain-text body and attachment names. In long threads Gmail collapses older messages, so only rendered (expanded) messages are returned.

Start building not clicking

Get started for free