Send Email

Node type: gmail_send_email · Version: 1 · Category: Communication Send only after explicit workflow approval. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

When to use this node

Send an approved transactional or notification email from a connected Gmail account.
Continue an existing thread after recipient logic has been reviewed.

Example: Send an approved report

Send a mapped summary and approved attachment to a fixed recipient.

Example settings

{
  "credentialId": "gmail-reports",
  "to": "ops@example.com",
  "cc": "",
  "bcc": "",
  "subject": "Daily report",
  "body": "{{nodes.ai.output.response}}",
  "htmlBody": "",
  "replyToMessage": "",
  "attachments": [
    "{{nodes.write.output.path}}"
  ]
}

This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector. Local paths must be selected, mapped from a trusted path, or covered by the runner’s approved boundary.

Keep recipient logic narrow and visible.
Put a Manual Approval node before Send Email for run-time review when appropriate.
Publish and approve the exact workflow revision before automatic use.

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.
`attachments`	array	`[]`	Approved attachment paths.

Automatic sending requires approval for the selected connection and recipient logic. A material change revokes that approval.

Workflow JSON

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

Default node configuration

{
  "type": "gmail_send_email",
  "version": 1,
  "configuration": {
    "credentialId": "",
    "to": "",
    "cc": "",
    "bcc": "",
    "subject": "",
    "body": "",
    "htmlBody": "",
    "replyToMessage": "",
    "attachments": []
  }
}

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

The node performs an external communication side effect and requires both general communication permission and revision-bound send approval.
Attachments must resolve to approved paths.
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

Changing recipient logic or other material workflow behavior revokes approval.
Retries can duplicate mail unless the surrounding workflow has a deduplication strategy.

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: Send an approved report

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Send an approved report

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Send an approved report

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides