> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/netofuse/modules/local-file.md).
# Local File
About The Local File NetoFuse module provides enriched asset context to Netography Fusion from a CSV or JSON file read from the local filesystem. It reads, transforms, and uploads Context Labels to th
The Local File NetoFuse module provides enriched asset context to Netography Fusion from a `CSV` or `JSON` file read from the local filesystem. It reads, transforms, and uploads [Context Labels](/enrich-traffic-with-context/labels.md) to the Netography Fusion API.
This may be used if you have a separate process that exports data to one of these formats and can save it to a filesystem. This can then handle converting that file to the appropriate Netography context label `CSV` format and automate the processing and uploading of that data.
The module will read files in a standard `CSV` or `JSON` format, using the file extension to determine the file type.
It supports defining a [context transform](/netofuse/context-transforms.md) to map fields to context label names and modify the values, just like other NetoFuse modules.
{% hint style="danger" %}
**đŸ›‘Using the NetoFuse upload command is usually the better option**
To use the local file module, you will need to modify the configuration for the module and then run the module. You can bypass these steps by using the [upload command](/netofuse/shell-commands.md#upload) instead. The upload command uses the `localfile` module to actually perform the work, so the results will be the same, but all the options are set on the command line instead of in a configuration file.
{% endhint %}
## Other options for importing context labels from files
See the [Generic Integration Capabilities](broken://pages/Fj84Zhn8MFIpj1Dv1BhA#generic-integration-capabilities) for additional options for importing context.
## Advanced configuration options
Multiple files can be imported with a single configuration, or you can use the advanced configuration to set multiple `localfile` module instances with unique transforms and settings. You may find that a single configuration file with multiple `localfile` instances and transforms defined is easier to manage than a script that executes multiple `netofuse upload` commands. Since `upload` acts as the command line front-end to configuring and running the `localfile` module, the end result will be the same.
---
# 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.fusion.vectra.ai/netofuse/modules/local-file.md?ask=&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.