Create Gmail Draft

Node type: gmail_create_draft · Version: 1 · Category: Communication Create an editable draft without sending. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

When to use this node

Prepare an email for human review without sending it.
Make an AI- or data-generated response visible in Gmail before delivery.

Example: Create a reviewed support reply

Map the sender, subject, and generated response into a draft on the original thread.

Example settings

{
  "credentialId": "gmail-support",
  "to": "{{trigger.email.from}}",
  "cc": "",
  "bcc": "",
  "subject": "Re: {{trigger.email.subject}}",
  "body": "{{nodes.ai.output.response}}",
  "htmlBody": "",
  "replyToMessage": "{{trigger.email.messageId}}"
}

This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector.

Map and validate at least one recipient.
Use replyToMessage when the draft belongs on an existing thread.
Open Gmail and review recipients and content before sending.

Configuration

Field	Type	Default	What it controls
`credentialId`	string	`""`	Reference to a connection stored in the operating-system credential vault.
`to`	string	`""`	Comma-separated or mapped recipient value.
`cc`	string	`""`	Optional CC recipients.
`bcc`	string	`""`	Optional BCC recipients.
`subject`	string	`""`	Email subject or approval subject.
`body`	string	`""`	JSON request body for POST, PUT, and PATCH requests.
`htmlBody`	string	`""`	Optional HTML email body.
`replyToMessage`	string	`""`	Optional Gmail message ID to reply to.

Drafts are the safer default because nothing is sent until a person reviews the message in Gmail.

Workflow JSON

The editor stores this node with the following implemented default configuration:

Default node configuration

{
  "type": "gmail_create_draft",
  "version": 1,
  "configuration": {
    "credentialId": "",
    "to": "",
    "cc": "",
    "bcc": "",
    "subject": "",
    "body": "",
    "htmlBody": "",
    "replyToMessage": ""
  }
}

Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

Inputs

This node has no typed ports in this direction.

Outputs

Port	Type	Required	Description
`result`	`any`	No	Result

Execution behavior

Creating a draft changes mailbox state but does not transmit the message to recipients.
The connection is resolved by the secure integration host and requires external communication permission.
The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

Common issues

When both body and htmlBody are used, verify they communicate the same content.
Generated recipients and content still need validation even though the action only creates a draft.

Where it can run

Desktop local runner
Paired self-hosted runner
Hosted runner

Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.

Node reference

Triggers

Logic

Data

Network

Browser

Communication

System

When to use this node

Example: Create a reviewed support reply

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Create a reviewed support reply

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Create a reviewed support reply

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides