> 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.md).

# Import from File

**Category:** Files

**Version:** 1.0

**Last updated:** June 15, 2026

**Author:** Any2Info

***

### Description

The Import From File node allows you to import files from a configured file system into your data flow.

This node can retrieve one or multiple files from a file system location and make them available for further processing within the data flow.

The configured path can reference either a single file or a directory:

* When a file is specified, that file is imported.
* When a directory is specified, all matching files are imported based on the configured search pattern.

The process works as follows:

1. Select a valid Connection.
2. Configure the Path to a file or directory.
3. Optionally enable Subdirectories to include files from nested folders.
4. Define a Search Pattern to filter the files that should be imported.
5. Execute the node.
6. The matching files are returned to the data flow.

***

### Configuration Options

#### Connection

Select the file system connection that should be used to access the files.

The selected connection determines where the node will search for files and folders.

This field is required.

#### Path

Specifies the file or folder location that should be imported.

This field is required.

The path may contain:

* A fixed path value
* A column mapping from a previous node

Examples:

* `C:\Import\customers.csv`
* `C:\Import`
* `\\Server\Shared\Invoices`

When a column mapping is used, the node must be executed using the **For Each Row** execution type.

#### Subdirectories

When enabled, the node searches all subdirectories below the configured path.

When disabled, only files located directly in the specified path are processed.

#### Search Pattern

Defines which files should be included during the import.

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\_" |

Only files matching the specified pattern are returned.

***

### Output

The node returns one record for each imported file.

The output contains the following fields:

| Field              | Description             |
| ------------------ | ----------------------- |
| FileName           | Name of the file        |
| FileExtension      | File extension          |
| FileSize           | File size in bytes      |
| FileLastAccessTime | Last access timestamp   |
| FileCreationTime   | File creation timestamp |
| FileContent        | File content            |

The output can be used by subsequent nodes for further processing.

### Tips & Best Practices

* Use specific search patterns to limit the number of imported files.
* Enable Subdirectories only when files may be stored in nested folders.
* Verify that the configured path exists and is accessible.
* Ensure the configured connection has sufficient permissions to access the specified location.

***

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