Data Collection and Storage Nodes

Data Collection nodes read data from pages, browsers, local files, or network requests and save results to workflow variables. Storage nodes write workflow data to local files. This guide covers all 15 Data Collection nodes.

Data Collection and Storage nodes

Read Page and Browser Data

Get URL

Reads the active tab address and saves it to an output variable. Choose:

• Complete URL: Includes scheme, path, and query parameters.
• Origin: Keeps only the website origin.
• Query parameter: Reads the value of a specified parameter.

For example, for:

https://example.com/products?page=2&category=books

the complete URL returns the entire value, Origin returns https://example.com, and a parameter of page returns 2.

Get Clipboard Content

Reads text from the system clipboard and saves it to a variable. Confirm that the clipboard source is trusted before running the workflow so passwords or account data do not enter later logs or files.

Reading the system clipboard requires the desktop client and operating system permission.

Get Element Data

Locates a page element and extracts selected data. Use a selector or saved element object as the source.

Available data:

• Element text.
• DOM object.
• iframe.
• Element source.
• Specified attribute.
• Specified child element.

Save the result to an output variable. DOM and focused element results are identified as element and can be used directly by downstream Click, Enter Text, or Hover nodes.

For an attribute, enter its actual name such as href, src, or data-id. Child extraction also requires a location rule.

Get Element Data configuration

Get Focused Element

Reads the element currently focused on the page and saves it as an element object variable. Use it with Focus Element, mouse clicks, or keyboard actions.

Get Focused Element

Example:

Focus Element → Get Focused Element → Enter Text

The final node selects the saved focused element object without entering another selector.

Use a saved focused element object

Save Data to Files

Save to File

Writes a text template to a local file. The file name and content can contain variables.

The default directory is the system Downloads directory, and the executor adds .txt. Do not add multiple extensions manually.

Content can combine fixed text and variables:

Task: ${task_name}
Profile: ${browser_name}
Result: ${product_title}

Save text configuration

Save to Excel

Writes selected variables as columns to a local Excel file. Enter a variable-enabled file name and select the columns to save.

The default directory is Downloads, and the executor adds .xlsx.

Choose descriptive variables for each column:

Variable	Excel column
product_name	Product name
product_price	Product price
product_url	Product page URL

Save Excel configuration

Default File Name

When Save to File or Save to Excel has no file name, both use the same base name during one run:

taskId_secondTimestamp

The executor adds an extension according to the node type. Add ${serial_number} or ${browser_name} when files from several profiles must be distinguished.

Local File Dependencies

Selecting a directory and writing text or Excel requires the ZYBrowser desktop client and local file permission. Confirm that the default Downloads directory is writable when a task moves to another computer.

Download a File

Downloads content from a file URL to a selected local directory.

Configure:

• File URL.
• Local destination directory.

Static URLs are format-checked during configuration. A URL containing variables is resolved at runtime. Confirm that the upstream node creates a complete URL with its required scheme.

The destination must exist and be writable on the computer running the task.

Import Local Materials

Import Excel Material

Reads a local Excel workbook and generates workflow variables from its first-row headers.

1. Select a local Excel file.
2. Let the node read the first-row headers.
3. Review the generated variable names.
4. Choose a row by profile number or save the complete table to an array variable.
5. Use the generated column variables downstream.

Only a static local path is read during design. A variable path is resolved at runtime, so a dynamic workbook is not read in the editor.

Import Excel material configuration

Header Rules

Every header must convert to a valid, unique variable name. Empty headers, duplicates after conversion, or invalid names fail validation.

Lowercase English and underscores are recommended:

Recommended header	Use
username	Account name
target_url	Target URL
keyword	Search term

Read a Row by Profile Number

Use the system variable serial_number so each profile reads its corresponding Excel row. A multi-profile task can assign different accounts or materials this way.

Enable Skip when no row matches the profile number to skip a profile without a row. When disabled, prepare data for every profile.

In addition to individual column variables, save the complete table to an array and process rows with For Each Data Item.

Excel material headers and data rows

Import TXT

Reads all content from a local text file into a variable. Use it for message templates, long text, or other plain-text materials.

When the path exists on only one computer, select it again after migrating the workflow.

Authenticator Code

Generates a time-based authenticator code from a secret and saves it to a variable. Enter the variable in a verification-code field downstream.

The secret is sensitive. Do not place it in notes, screenshots, debug descriptions, or public shares, and restrict workflow and runtime-computer access.

Listen for Page Requests

Listen for Request Trigger

Listens for a request matching a target URL. Extract request content, a named request-header field, or a GET parameter into output variables.

Configure the listener before the page action that triggers the request:

Listen for Request Trigger → Click Element → downstream processing

Use a stable rule that identifies the target API without matching a large number of unrelated requests.

Listen for Request Results

Listens for the response to a request matching a target URL and saves it to a variable. Pass it to Parse JSON or Extract Field.

Listen for Request Results → Click Element → Parse JSON → Extract Field

Stop Page Listener

Stops the current page request listener. It has no business configuration.

Stop it as soon as it is no longer needed so later page actions do not collect unrelated data. With several listeners, add a Stop node at the end of each business section.

Request listener workflow

Cookie Nodes

Get Page Cookies

Reads cookies for the active page and saves them to a variable. Cookies may contain login credentials and should be used only when necessary.

Clear Page Cookies

Clears cookies for the active page without additional configuration. The page may sign out or change business state, so place it near the end and validate it in a test profile first.

Protect Sensitive Data

Cookies, authenticator secrets, account details, and request headers can contain authentication information. Never place real values in public files, screenshots, share descriptions, or uncontrolled logs.

Troubleshooting

Output Variable Missing Downstream

Confirm that the output name is valid and that the using node is on a reachable downstream path. A variable from one branch does not automatically appear in an unrelated branch.

Excel Header Validation Fails

Check for empty headers, characters that cannot form a variable name, or duplicates after conversion. Use short, unique lowercase English names for the first row.

File Missing After Save

Save to File and Save to Excel use Downloads by default. Check the output path in Run History; when the log includes the path and name, use it to locate the file.

Dynamic Path Has No Excel Headers in the Editor

This is expected during design. Static local paths are read ahead of time; variable paths resolve at runtime. Select a test workbook with the real headers if column variables are required during design.

Related Guides

• Data Processing Nodes: Parse JSON, extract with regular expressions, and extract fields.
• Variables and Data: Learn output variables, arrays, and objects.
• Flow Control Nodes: Loop through an Excel table or page elements.
• Run History: Locate output files in formal task logs.