Skip to main content
Node type: list_folder · Version: 1 · Category: Data List files in an approved folder. 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

  • Discover files for a batch workflow.
  • Count or filter entries before deciding whether to continue.

​
Example: List pending CSV files

List matching CSV files in one approved folder without descending into subfolders.
Example settings
This shows the important settings, not a complete exported node. Local paths must be selected, mapped from a trusted path, or covered by the runner’s approved boundary.
  1. Select the folder through the picker.
  2. Use the narrowest pattern that represents eligible files.
  3. Map count to Condition or entries to Code for iteration and selection.

​
Configuration

A listing fails after 10000 matching entries to keep execution output bounded.

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
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

​
Outputs

​
Execution behavior

  • The output contains an entries array and total count.
  • recursive changes the search boundary to include nested folders but does not grant access outside the approved root.
  • The editor catalogue declares entries (array), count (number) 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

  • Pattern matching applies to names; verify behavior with representative nested paths.
  • A very broad recursive listing can create a large execution payload.

​
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.