Sign in

v2

latestOpenAPI 3.1.02026-08-05298342605.2 KB
Capability Sources

Create a Gmail draft or threaded reply draft without attachments

Creates a plain-text Gmail draft in the calling member own mailbox. For workspace attachments, use the openwork-cloud-uploads gmail_create_draft_with_attachments action so file bytes stay outside model context. Set threadId for replies and forwards. Always share the returned draftUrl.

post/v1/capabilities/google-workspace/gmail-drafts

Request body

tostring required

Recipient email address.

ccstring

Optional comma-separated Cc email addresses.

bccstring

Optional comma-separated Bcc email addresses.

subjectstring required

Draft subject line. For replies or forwards, include threadId; subjects starting with Re: or Fwd: are rejected without threadId so the draft stays on the existing conversation.

bodystring required

Plain-text draft body. Write plain prose with no markdown syntax, separate paragraphs with blank lines, and do not hard-wrap prose. For threaded drafts, the server appends the quoted conversation automatically; do not include quoted history.

threadIdstring

Gmail thread id to reply on. Required for replies and forwards; get it from the gmail-messages capability. When set, the draft is attached to that thread as a reply — keep the thread's subject (e.g. 'Re: …').

Response

Draft created.

oktrue required
draftIdstring required
messageIdstring nullable required
draftUrlstring nullable required

Gmail URL for the ready-to-send draft. Always share draftUrl with the user so they can open the draft in Gmail for review and send.

threadUrlstring nullable required

Gmail URL for the conversation thread when this draft is a threaded reply.

tostring required
subjectstring required
threadIdstring nullable required
quotedHistoryIncludedboolean required

True when quoted conversation history was included by the server or already present in the request body.