Screenshot

Node type: screenshot · Version: 1 · Category: Browser Capture viewport, page or element. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

When to use this node

Capture visual evidence at an important checkpoint.
Record a viewport, full page, or one selected element for debugging.

Example: Capture a full report page

Save a full-page image in execution history with a 10 MiB limit.

Example settings

{
  "mode": "full_page",
  "includeInHistory": true,
  "maximumBytes": 10485760,
  "timeoutMs": 30000
}

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

Place Screenshot after the page state you want to prove.
Choose the smallest capture area that contains the needed evidence.
Inspect privacy-sensitive content before enabling retained history artifacts.

Configuration

Field	Type	Default	What it controls
`mode`	string	`"viewport"`	Screenshot capture area. Values: `viewport`, `full_page`, `element`.
`includeInHistory`	boolean	`true`	Attach the screenshot artifact to execution history.
`maximumBytes`	number	`10485760`	Maximum accepted file, response, screenshot, or download size in bytes.
`timeoutMs`	number	`30000`	Maximum time for this operation in milliseconds.
`locator`	locator	—	Recorded locator bundle. sndbox prefers accessible role/name data and retains fallbacks. Shown when `mode` is `element`.

History artifacts follow the configured screenshot retention policy.

Workflow JSON

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

Default node configuration

{
  "type": "screenshot",
  "version": 1,
  "configuration": {
    "mode": "viewport",
    "includeInHistory": true,
    "maximumBytes": 10485760,
    "timeoutMs": 30000
  }
}

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
`path`	`path`	No	Screenshot path

Execution behavior

The output is a trusted screenshot path; history attachment is controlled separately by includeInHistory.
Element mode requires a recorded locator and all modes enforce maximumBytes.
The editor catalogue declares path (path) 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

Full-page images can exceed the size limit on long pages.
Screenshots can capture personal data or secrets visible in the page even when text logs are redacted.

Where it can run

Desktop local runner
Paired self-hosted runner
Managed browser worker

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: Capture a full report page

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Capture a full report page

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Capture a full report page

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides