> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/files/load-file.md).

# Load File

### Overview

The **Load File Component** reads a file stored in the system using its unique file ID and sends its content to the output port. It is useful for processing stored files in workflows.

### Usage

This component is used to retrieve file content for further processing or validation in workflows.

#### Properties

| Property | Type     | Description                                     |
| -------- | -------- | ----------------------------------------------- |
| `fileId` | `string` | The unique identifier of the file to be loaded. |

#### Input Ports

| Port | Description                     |
| ---- | ------------------------------- |
| `in` | Accepts the file ID to be read. |

#### Output Ports

| Port      | Description                           |
| --------- | ------------------------------------- |
| `content` | Emits the file’s content as a string. |

#### Processing Logic

1. **Receives Input Data**:
   * Accepts a `fileId` that identifies the stored file.
2. **Reads File Content**:
   * Opens a stream to read the file contents.
   * Accumulates the content as data chunks arrive.
3. **Sends File Content**:
   * Emits the full file content to the `content` output port.
   * If an error occurs (e.g., file not found), it is logged or raised appropriately.

#### Output Data Schema

| Property  | Type     | Description                              |
| --------- | -------- | ---------------------------------------- |
| `content` | `string` | The complete content of the loaded file. |

### Notes

* **Retrieves Full File Content**: Useful for workflows requiring file content processing.
* **Supports Various File Types**: Works with text-based and structured data files.
* **Ideal for Data Processing Workflows**: Enables automated retrieval of stored files for further actions.

This component is essential for workflows that require accessing and processing stored file content dynamically.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/utils/files/load-file.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.