Manual Approval

Node type: approval · Version: 1 · Category: Logic Pause for local review. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

When to use this node

Pause before sending, deleting, publishing, or performing another consequential action.
Show the operator a resolved preview and attachments at the moment of decision.

Example: Approve an outbound email

Present the recipient, subject, and message preview, then continue to Send Email only after approval.

Example settings

{
  "proposedAction": "Send the prepared customer reply",
  "recipient": "{{nodes.compose.output.to}}",
  "subject": "{{nodes.compose.output.subject}}",
  "messagePreview": "{{nodes.compose.output.body}}",
  "attachments": [],
  "expiresInMinutes": 60
}

This shows the important settings, not a complete exported node.

Place Manual Approval directly before the guarded action.
Map enough resolved context for an informed decision.
Handle rejection or expiry as an expected failed outcome in operations.

Configuration

Field	Type	Default	What it controls
`proposedAction`	string	`""`	Plain-language action shown to the reviewer.
`recipient`	string	`""`	Optional recipient filter.
`subject`	string	`""`	Email subject or approval subject.
`messagePreview`	string	`""`	Content preview shown before approval.
`attachments`	array	`[]`	Approved attachment paths.
`expiresInMinutes`	number	`60`	Time before the local approval expires, from 1 to 10080 minutes.

The execution pauses locally and appears in Pending approvals and the system tray until it is approved, rejected, or expires.

Workflow JSON

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

Default node configuration

{
  "type": "approval",
  "version": 1,
  "configuration": {
    "proposedAction": "",
    "recipient": "",
    "subject": "",
    "messagePreview": "",
    "attachments": [],
    "expiresInMinutes": 60
  }
}

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 execution pauses locally and appears in Pending approvals and the system tray.
Approval, rejection, cancellation, and expiry are recorded against this execution; approval does not silently broaden workflow permissions.
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

Closing or disconnecting the local app can prevent a reviewer from acting before expiry.
Do not use vague proposedAction text: the reviewer should know exactly what changes and where.

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: Approve an outbound email

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Approve an outbound email

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Approve an outbound email

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides