> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/files/import-from-file-system.md).

# Import from File System

**Category:** Files

**Version:** 1.0

**Last updated:** June 15, 2026

**Author:** Any2Info

***

### Description

The Import from File System node allows you to retrieve information about files and folders from a configured file system location.

The node searches a selected folder and returns files and/or directories that match the configured search criteria. This information can be used by subsequent nodes for filtering, processing, or file import operations.

Unlike the Import From File node, this node does not import the content of files. Instead, it returns information about the matching files and folders.

The process works as follows:

1. Select a valid Connection.
2. Select the Folder that should be searched.
3. Optionally enable Subdirectories to include nested folders.
4. Configure search patterns for directories and files.
5. Specify whether directories, files, or both should be included.
6. Execute the node.
7. The matching files and folders are returned to the data flow.

***

### Configuration Options

#### Connection

Select the file system connection that should be used.

The selected connection determines which file system location can be accessed.

This field is required.

#### Folder

Specifies the folder that should be searched.

This field is required.

The selected folder acts as the starting point for the search operation.

#### Subdirectories

When enabled, all subdirectories below the selected folder are included in the search.

When disabled, only the selected folder is searched.

#### Search Pattern (Directories)

Defines which directories should be included.

The search pattern supports wildcard filtering.

Examples:

| Pattern    | Description                         |
| ---------- | ----------------------------------- |
| `*`        | All directories                     |
| `Invoice*` | Directories starting with "Invoice" |
| `2026*`    | Directories starting with "2026"    |

#### Search Pattern (Files)

Defines which files should be included.

The search pattern supports wildcard filtering.

Examples:

| Pattern         | Description                     |
| --------------- | ------------------------------- |
| `*.*`           | All files                       |
| `*.csv`         | All CSV files                   |
| `*.xml`         | All XML files                   |
| `invoice_*.pdf` | Files starting with "invoice\_" |

#### Directories

When enabled, matching directories are included in the result.

When disabled, directories are excluded.

#### Files

When enabled, matching files are included in the result.

When disabled, files are excluded.

***

### Output

The node returns all files and/or directories that match the configured search criteria.

The returned records can be used by subsequent nodes for filtering, processing, or file import operations.

To import the actual content of files, use the Import From File node.

***

### Tips & Best Practices

* Use specific search patterns to reduce the number of returned results.
* Enable Subdirectories only when recursive searching is required.
* Use the Directories and Files options to limit the output to only the required object types.
* Use this node to locate files before processing them with the Import From File node.
* Verify that the configured connection has sufficient permissions to access the selected folder.

***

### Changelog <a href="#changelog" id="changelog"></a>

| Version | Date          | Change                               |
| ------- | ------------- | ------------------------------------ |
| 1.0     | June 15, 2026 | Initial documentation version added. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/files/import-from-file-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.