Extract Data

Node type: extract_data · Version: 1 · Category: Browser Extract structured values from the page. 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

Read text, an attribute, a link, an image URL, or tabular data from a page.
Turn one or many matched elements into structured workflow data.

Example: Extract all visible product names

Record a representative product heading and return all unique matches under the field name products.

Example settings

{
  "locator": {
    "primary": {
      "kind": "css",
      "value": "[data-testid='product-name']"
    },
    "alternatives": []
  },
  "extract": "text",
  "fieldName": "products",
  "repeated": true,
  "fields": {},
  "timeoutMs": 30000
}

This shows the important settings, not a complete exported node. The locator is shortened for readability; use the recorder to create the complete structured locator bundle.

Record the narrowest stable repeated target.
Choose the extraction kind and a descriptive field name.
Test against empty, single-result, and multi-result pages.

Configuration

Field	Type	Default	What it controls
`locator`	locator	`null`	Recorded locator bundle. sndbox prefers accessible role/name data and retains fallbacks.
`extract`	string	`"text"`	Kind of value read from the selected page element. Values: `text`, `attribute`, `link`, `image_source`, `table`.
`fieldName`	string	`"value"`	Name used for the extracted output value.
`repeated`	boolean	`false`	Return all unique matches as a list instead of one value.
`fields`	object	`{}`	Column mapping used for table extraction, or Discord embed field objects.
`timeoutMs`	number	`30000`	Maximum time for this operation in milliseconds.
`attribute`	any	—	HTML attribute name when extracting an attribute. Shown when `extract` is `attribute`.

Workflow JSON

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

Default node configuration

{
  "type": "extract_data",
  "version": 1,
  "configuration": {
    "locator": null,
    "extract": "text",
    "fieldName": "value",
    "repeated": false,
    "fields": {},
    "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
`value`	`any`	No	Extracted value

Execution behavior

repeated returns a list of unique matches; otherwise the node expects a single resolved value.
Attribute extraction additionally requires the attribute name, while table extraction uses the fields mapping.
The editor catalogue declares value (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

A locator that matches layout containers can return whitespace or duplicate text.
Extracted page content is untrusted external data; validate it before commands, paths, or outbound messages.

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: Extract all visible product names

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Extract all visible product names

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Extract all visible product names

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides