Filesystem

​

Overview

The Filesystem package provides pre-configured examples for building integrations that read from and write to files stored on a local or network filesystem. These examples cover the core components of a complete integration flow, including Incoming configurations, Outgoing configurations, and Transformers. Whether you need to import files, process their contents, export generated files, or automate file-based workflows, these templates offer a practical starting point that you can customize to fit your specific requirements.

​

General Information

The Filesystem package includes examples for the following integration scenarios:

1. Reading data from a specific file
2. Listing and processing multiple files from a directory
3. Transforming file contents before further processing
4. Writing processed data to a file on the filesystem

Each example shows how the different Alumio components work together in a typical file-based integration:

• Incoming Configuration –– retrieves files or file contents from the filesystem
• Transformer –– processes, normalizes, or restructures the retrieved data
• Outgoing Configuration –– writes the transformed data to a target file or directory

These examples cover common filesystem integration use cases and serve as a solid starting point for building your own integrations.

​

Package Contents

The package includes the following example configurations: 1. Filesystem: File Subscriber Incoming
Shows how to read data from a specific file using a Filesystem Subscriber. Useful when the file location is known and data needs to be imported directly from a single file. 2. Filesystem: Listing Subscriber Incoming
Shows how to retrieve multiple files from a directory using a Filesystem Listing Subscriber. Commonly used for batch processing, where all files matching specific criteria are imported automatically. 3. Write File to a Filesystem Transformer
Shows how to prepare and transform data before writing it to a file. Demonstrates converting incoming data into the structure or format required by the target file. 4. Write File to a Filesystem Outgoing
Shows how to write processed data to the filesystem. Can be used to export integration results, generate reports, or create files consumed by another system.

​

Typical Use Cases

The Filesystem package supports a variety of file-based integration scenarios, including:

• Importing CSV, JSON, XML, or text files
• Processing files generated by ERP, PIM, or other business systems
• Exporting processed data for external applications
• Automating file exchange between systems
• Creating scheduled file import and export workflows

​

Customization

These configurations are meant to be reused as templates. After importing the package, you can customize:

• File and directory paths
• File formats
• Transformers used to process the data
• Scheduling and execution behavior
• Additional routing and mapping logic.

This lets you quickly adapt the examples to your own filesystem integration requirements while following Alumio’s recommended integration patterns.

​

Integration Flow Example

A typical Filesystem integration flow works as follows:

1. Incoming configuration retrieves file data from the source filesystem or directory.
2. Transformer processes and converts the data into the required format.
3. Outgoing configuration writes the processed data to a target file or directory.
4. Route connects all components and manages the data flow between them.

Using these templates, you can quickly create reliable filesystem integrations without building every configuration from scratch.

​

Template Import

Follow these steps to import a template to Alumio:

1. Log in to your Alumio dashboard.
2. Navigate to More > System > Import/Export

3. Click to browse or drag and drop ndjson file to upload it.

4. Click Import Configurations to start the import.