v26.01: Working with Read Nodes

Read nodes retrieve data from various source systems and make it available to downstream nodes in the workflow. The Read category provides various node types, each designed for specific data sources.

Available Read Node Types

Configuration Layout

The Configuration layout section determines which dimensions and metrics to include and how to organize them in the output.

The layout consists of three sections that work together to define the data structure.

Each dimension displays controls: Filter Icon (member selector), Ellipsis Menu (Move/Remove options), Preferences (Rows only), and Expand/Collapse.

v26.03: Update List

When dimensions are removed from any layout section, they automatically move to the Update List. The Update List maintains all dimensions from the source that are not currently visible in the layout sections.

To restore dimensions, select Update List > check dimensions > select Okay.

Note: Every dimension from the source must appear either in the Layout sections or in the Update List at all times. This ensures complete data structure definition.

v26.05: Configuring File Upload Node

The File Upload node provides a file-based data source for workflows. Workflow designers configure the node at design time with an allowed file type and a sample file for preview; users supply the actual file at runtime through the Run dialog. The node passes a file reference to a downstream File Reader node — it does not produce tabular output of its own.

v26.07:  File Upload now accepts both CSV and Excel files, eliminating file format conversion workflows. Users no longer need to convert Excel files to CSV before uploading.

To configure a File Upload node:

1. Click + Add Node from the Level 2 header. The Add Node dialog opens.

2. Select Read from the left panel.

3. Select File Upload from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to File Upload_[n].
   v26.07:  Allowed File Types	Dropdown with CSV and Excel pre-selected. Supports single-sheet and multi-sheet Excel files.
   Sample File	Select Choose file to open the OS file picker and select a representative file. The filename appears beside the button (truncated with an ellipsis if too long); before any file is selected, the field shows No file chosen. The sample file persists across publish or reopen, is shared with all workflow users (not user-scoped), and is never added to the Previously Uploaded Files history.
   v26.05: Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. Select Publish in the Level 2 header to save the configuration.

   Two additional controls become available in the Level 2 header:

   • Refresh: Re-reads source data and previews unpublished layout changes without requiring a full publish.

   • View/Edit Mode: Toggles whether the configuration panel displays while maintaining the read-only data grid.

v26.07: Supported File Formats

The File Upload node accepts both CSV and Excel files.

• CSV files include standard comma-separated values, tab-delimited files, and custom delimiter files (which are configurable at runtime via Encoding and Delimiter controls).

• Excel files include single-sheet and multi-sheet Excel workbooks (.xlsx).

• When uploading a multi-sheet Excel file, the File Reader node allows you to select which sheet to read.

Sample File vs. Runtime File

The sample file is used only for design-time preview — it allows the downstream File Reader node to be configured against a representative file structure. At runtime, users supply the actual file through the Run dialog (see Running Workflows with File Upload Nodes). The runtime file may have different content than the sample file.

v26.07: The sample file and runtime file can be in different formats (for example, sample is CSV, runtime is Excel), as long as the structure is compatible with the File Reader configuration.

Previously Uploaded Files

After a workflow is run with a File Upload node, the runtime file appears in a Previously Uploaded Files section on the node, scoped to the logged-in user. Files are listed in reverse chronological order with the timestamp and trigger icon. The sample file is never added to this list.

Multiple File Upload Nodes

A workflow can contain multiple File Upload nodes. Each is independent — its name, allowed file type, sample file, and upload history are all node-scoped. At runtime, each node gets its own block in the Run dialog, and the Run button is enabled only when all File Upload nodes have a valid file.

Managing Runtime Upload and File History

At runtime, the Run dialog displays a dedicated File Uploads section for each File Upload node, with controls for Choose file, Encoding, and Delimiter. The Run button stays disabled until every File Upload node has a valid file. A Previously Uploaded Files section, scoped to the logged-in user, lists past runtime uploads in reverse chronological order for audit.

v26.07:  When uploading Excel files, a Sheet Selection dropdown appears if the file contains multiple sheets, allowing users to specify which sheet to read.

Configuring File Reader Node

The File Reader node parses a file received from a File Upload node into a tabular dataset for downstream consumption.

v26.07: With v26.07, File Reader now supports separate configuration for header position and data position, enabling precise control over where headers and data begin in both Excel and CSV files.

v26.05: 

Prerequisite

A File Upload node must already exist in the workflow. The File Reader cannot be configured without an upstream File Upload to source from.

To configure a File Reader node:

1. Click + Add Node from the Level 2 header. The Add Node dialog opens.

2. Select Read from the left panel.

3. Select File Reader from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to File Reader_[n].
   Source	Select an existing File Upload node from the dropdown. The dropdown lists all File Upload nodes in the workflow and updates dynamically as nodes are added, removed, or renamed.
   Header Start Cell v26.07:	Cell reference defining the header row and leftmost column (for example, A1 or B3). The Header Start Cell row is treated as the header; column detection begins at the specified column. This setting is independent from the Data Start Cell, allowing headers and data to begin at different rows. Note: v26.08: For Excel files, you can specify any valid cell reference. For CSV files, the header is always fixed to the first row and first column.
   Data Start Cell v26.07:	Cell reference defining where the data region begins (for example, A2 or B4). Rows above this cell are skipped; the Data Start Cell row is the first data row. This setting is independent from the Header Start Cell, allowing flexible file layouts with metadata or multiple header rows. Note: v26.08: When swapping file types (Excel → CSV), both Header and Data Start Cell reset automatically to the default starting position, with a warning to prevent mismatches.
   Column Selection	Choose All columns (default) to include every column from the Header Start Cell column onward, or Specific columns to open a checklist of header names alongside positional references (Column A, B, C…) and select the columns to include.
   v26.05: Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

   Note: v26.08: After editing Header or Data Start Cell, or swapping file types, the Refresh button appears. Until clicked, the column list remains unchanged, preserving downstream mappings. A stale indicator shows when columns are outdated, prompting users to refresh.

5. Select Publish in the Level 2 header to save the configuration.

   The system validates the configuration and displays retrieved data in the grid viewer below the canvas. Data appears in read-only format structured according to the configured layout.

   Two additional controls become available in the Level 2 header:

   • Refresh: Re-reads source data and previews unpublished layout changes without requiring a full publish.

   • View/Edit Mode: Toggles whether the configuration panel displays while maintaining the read-only data grid.[MG3.1]

v26.07: Independent Header and Data Position Control

Header Start Cell and Data Start Cell are now independent settings, allowing you to handle files with non-standard layouts:

• Scenario 1: File with metadata rows before headers

  • Header Start Cell: B5 (headers begin at row 5)

  • Data Start Cell: B6 (data begins at row 6)

• Scenario 2: File with multiple header rows

  • Header Start Cell: A1 (first header row)

  • Data Start Cell: A3 (data begins after second header row at row 3)

• Scenario 3: File with leading columns to skip

  • Header Start Cell: C1 (headers begin at column C)

  • Data Start Cell: C2 (data begins at column C, row 2)

Column detection updates automatically whenever you change the Header or Data Start Cell positions, ensuring downstream mappings stay in sync with the new layout.

Column position vs. header name

All downstream mapping is based on column position (Column A, B, C…), not header name. If the runtime file has different header text than the sample file (for example, “Account” renamed to “ACC”), the mapping remains intact because it follows column position. Files with blank or missing headers are still readable through the same positional reference.

Output

The File Reader output is a flat tabular dataset (rows × selected columns). All values are read as text. Downstream nodes (Mapping, SQL, Write) handle any type conversion.

Failure conditions

The node fails at runtime if:

• The uploaded file does not match the File Upload configuration (for example, delimiter mismatch).

• The uploaded file is empty (0 bytes or no content).

• v26.07: The Header Start Cell row is beyond the file's row count.

• v26.07: The Data Start Cell row is beyond the file's row count.

• The connected File Upload node has been deleted.

Multiple File Reader nodes

One File Upload node can feed multiple independent File Reader nodes, each with its own Header Start Cell, Data Start Cell, and Column Selection configuration. If the File Upload node is deleted, all connected File Reader nodes become invalid until a new File Upload source is selected.

v26.02: Configuring Remote Table Node

Remote Table nodes incorporate external data from remote table connections into workflow pipelines.

To configure a Remote Table node:

1. Click + Add Node from the Level 2 header. The Add Node dialog opens.

2. Select Read from the left panel.

3. Select Remote Table from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to Remote Table_[n].
   Source	Select a remote table using the inline selector. All dimensions from the selected remote table are automatically added to Rows.
   Layout	Configure Rows and Filters sections (no Columns section).
   v26.05: Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. Select Publish in the Level 2 header to save the configuration.

   The system validates the configuration and displays retrieved data in the grid viewer below the canvas. Data appears in read-only format structured according to the configured layout.

   Two additional controls become available in the Level 2 header:

   • Refresh: Re-reads source data and previews unpublished layout changes without requiring a full publish.

   • View/Edit Mode: Toggles whether the configuration panel displays while maintaining the read-only data grid.

v26.04: All dimensions from the selected remote table are automatically added to Rows on source selection. Remote table dimensions do not have hierarchical relationships. Remote Table Read nodes support workflow parameter references for dynamic data filtering.

Configuring Sheet Node

Sheet nodes retrieve data from sheets within the workspace.

To configure a Sheet node:

1. Click + Add Node. The Add Node dialog opens.

2. Select Read from the left panel.

3. Select Sheet from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to Sheet_[n].
   Subtype	Read-only field showing the selected data type.
   Source	Select a sheet using the inline selector.
   Layout	Configure Rows, Columns, and Filters sections.
   v26.05:  Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. Select Publish in the Level 2 header to save the configuration.

   The system validates the configuration and displays retrieved data in the grid viewer below the canvas. Data appears in read-only format structured according to the configured layout.

   Two additional controls become available in the Level 2 header:

   • Refresh: Re-reads source data and previews unpublished layout changes without requiring a full publish.

   • View/Edit Mode: Toggles whether the configuration panel displays while maintaining the read-only data grid.

Note: Sheet nodes are the only Read data type with a Columns section in the layout. The Columns section supports dimensions and metrics.

v26.02:  Configuring Transaction Table Node

Transaction Table nodes retrieve data from transaction tables within the system.

To configure a Transaction Table node:

1. Click + Add Node. The Add Node dialog opens.

2. Select Read from the left panel.

3. Select Transaction Table from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to Transaction Table_[n].
   Source	Select a transaction table using the inline selector.
   Layout	Configure Rows and Filters sections (no Columns section).
   v26.05:  Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. Select Publish in the Level 2 header to save the configuration.

   The system validates the configuration and displays retrieved data in the grid viewer below the canvas. Data appears in read-only format structured according to the configured layout.

   After publishing, two additional controls become available in the Level 2 header:

   • Refresh: Re-reads source data and previews unpublished layout changes without requiring a full publish.

   • View/Edit Mode: Toggles whether the configuration panel displays while maintaining the read-only data grid.