App Logo
mail.google.com

Update a Gmail draft

Automatically update a Gmail draft on mail.google.com. Change the subject and/or body of an existing Gmail draft, identified by the id the drafts listing gives you. Whichever field you leave out keeps its current value; a field you pass replaces what was there rather than appending to it. The draft's current contents are read first, so asking for what it already says makes no change and says so. Gmail issues a draft a new id every time it is saved, so the id you passed in stops existing and the new one is returned — use that for any follow-up. The conversation id stays the same and is returned as the stable handle. Recipients are not touched by this script.

Input

draftId required

The draft's current id, as returned by the drafts listing: a new message or a reply saved inside a conversation. Note Gmail replaces this id on every save, so use a freshly listed one.

body optional

Replacement body text. This replaces the whole body rather than adding to it; for a reply, the quoted message below the body stays as it is. Pass an empty string to clear it. Omit to leave the body as it is.

account optional

Google account email whose draft this is. Without it Gmail opens the first signed-in account (u/0), which may not be the one holding the draft when several accounts share the browser.

subject optional

Replacement subject line. Pass an empty string to clear it. Omit to leave the subject as it is. A reply's subject follows its conversation and cannot be changed: a different subject for a reply is refused and nothing is written.

Output

after required

What the draft said after the edit, read back from the composer. For a reply, the body is the text above the quoted message.

before required

What the draft said before the edit. For a reply the subject is the one it carries from its conversation, and the body is the text above the quoted message.

changed required

Which fields were actually written. Empty when nothing needed changing.

draftId required

The draft's id AFTER the edit. Gmail mints a new one on every save, so this differs from the id passed in whenever something was written. Use this for follow-up calls.

account_used required

The Gmail account the draft was edited in, read from the session rather than assumed.

already_present required

True when the draft already said exactly what was asked for, so nothing was written.

verified_on_page required

True when Gmail confirmed the edit was saved: its answer to the save, or the Drafts list, shows the draft with the new subject and body under its new id.

isReply optional

True when the draft is a reply saved inside a conversation, false for a new message.

threadId optional

Id of the conversation holding the draft. Unlike the draft id this survives a save, which makes it the durable handle for the same draft over time.

verifiedBy optional

How the save was confirmed, when something was written: 'server' is Gmail's own answer to the save, which echoes the saved draft; 'drafts_list' is the draft found in the Drafts list under a new id with the new content, used when another Gmail tab in the browser saved it.

previousDraftId optional

The id that was passed in, which Gmail has now retired.

FAQ

Change the subject and/or body of an existing Gmail draft, identified by the id the drafts listing gives you. Whichever field you leave out keeps its current value; a field you pass replaces what was there rather than appending to it. The draft's current contents are read first, so asking for what it already says makes no change and says so. Gmail issues a draft a new id every time it is saved, so the id you passed in stops existing and the new one is returned — use that for any follow-up. The conversation id stays the same and is returned as the stable handle. Recipients are not touched by this script.
Ask an AI agent connected to Reduck to run reduck/mail.google.com/update_draft, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/mail.google.com/update_draft
You do not need one. "Update a Gmail draft" 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: draftId. Optional: body, account, subject.
It returns after, before, changed, draftId, isReply, threadId, verifiedBy, account_used, already_present, previousDraftId, verified_on_page.
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/update_draft, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/mail.google.com/update_draft
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