Getting Started
Basic Concept
Monitor a folder for new files and start the next transfer automatically
With manual file transfer, each new file requires someone to locate the file, select a destination, and start the transfer.
In environments such as business systems, batch servers, media equipment, and backup systems where files are created continuously in designated folders, the same transfer task may need to be repeated every time a new file appears.
For example, a batch job may generate a result file in /data/outgoing/, or new reports and backup files may be saved to a designated folder and need to be transferred immediately to another server or storage system.
With Hot Folder in INNORIX Flow, you can monitor a designated folder and start a transfer when a file matching configured conditions is created or modified.
Instead of selecting files manually, use the folder where files are created as the transfer starting point and automatically move detected files to the designated system or storage.
┌─────────────────────┐
│ Hot Folder │
│ │
│ /data/outgoing/ │
│ │
│ + report.csv │
│ + result.zip │
└──────────┬──────────┘
│
│ File Created
▼
File Detected
│
▼
Transfer Start
│
▼
Target System
Hot Folder can be used as the starting condition for a variety of automated transfer flows depending on how files are created.
| File Creation Environment | Hot Folder Use |
|---|---|
| Business System | Automatically transfer output files to the next system after processing |
| Windows PC | Detect new work files saved to a designated folder |
| Linux Server | Transfer result files generated after a batch job completes |
| Media Equipment | Automatically collect newly created video and image files |
| Backup System | Transfer completed backup files to remote storage |
For example, when a batch job creates a file, Hot Folder can detect it and transfer it to the configured Target. After the transfer completes, you can optionally start the next Flow or connect a follow-up processing task.
Batch Job
│
▼
Result File Created
│
▼
Hot Folder Detection
│
▼
File Transfer
│
├──────────────┐
▼ ▼
Target Server Next Process
This creates an automated file flow from file creation → Hot Folder detection → automatic transfer → result verification or next-task execution, without requiring someone to start the transfer after the file is ready.
Detection Flow
Automate the flow from file changes to delivery to the target system
Hot Folder automatic transfer starts when a file is created or modified.
When a file matching the configured conditions is detected in the designated folder, it is selected for transfer and sent automatically to the configured Target.
① File created or modified
│
▼
② Hot Folder detection
│
▼
③ Check transfer conditions
│
├── Conditions not met ──► Continue monitoring
│
▼
④ Run automatic transfer
│
▼
⑤ Apply to Target
│
▼
⑥ Review execution results
Because the file-creation location and transfer target are connected in advance, this reduces repetitive work between file preparation and transfer start.
Automation Benefits
Reduce repetitive work required to review files and start transfers manually
Traditionally, after a new file is created, someone may need to review it, select a transfer destination, and start the job.
With Hot Folder, file creation itself can serve as the starting condition for the transfer.
| Category | Manual Transfer | Hot Folder Automatic Transfer |
|---|---|---|
| File Review | Staff check for new files | Folder state is monitored automatically |
| Transfer Start | Start the job manually | Start automatically based on conditions |
| Target Selection | Confirm for each execution | Target is connected in advance |
| Repeated Work | Repeat the same steps for every file | Process automatically based on created files |
| Result Review | Review each transfer after completion | Review based on execution results |
For example, if a business system generates a result file every day, you can configure the flow as follows.
Business System
│
│ Create result_2026-09-02.zip
▼
┌─────────────────┐
│ Hot Folder │
│ /data/export/ │
└────────┬────────┘
│
│ Auto Transfer
▼
┌─────────────────┐
│ Remote Storage │
└─────────────────┘
This connects file creation → automatic detection → transfer → target delivery → result verification in one automated flow.
IT Engineers
Detection Setup
Connect the device and Hot Folder where file changes should be monitored
IT engineers first connect the device where files are created or modified as the Source and specify the folder to monitor automatically.
You can configure multiple Hot Folders on one device or connect different folders to separate transfer jobs by workflow.
┌───────────────────────┐
│ Source Device │
│ │
│ ├── /export/report/ │──► Flow A
│ │ │
│ └── /export/media/ │──► Flow B
│ │
└───────────────────────┘
When configuring Hot Folder, folders can be separated according to file-creation location and workflow.
| Configuration Basis | Example |
|---|---|
| By Workflow | Separate folders for reports, settlements, and result files |
| By System | Connect a separate Source for each generating system |
| By File Type | Separate video, image, and data files |
| By Target | Configure a separate Hot Folder for each Target |
This lets you connect different types of files generated on one device to the appropriate transfer flows.
Detection Conditions
Distinguish which new and modified files should be transferred automatically
Instead of transferring every file change, configure conditions so only files required for the workflow are processed automatically.
For example, you can transfer only newly created files or also reprocess existing files when they are modified.
File Event
│
├── Created ────────────┐
│ │
├── Modified ───────┐ │
│ │ │
▼ ▼ ▼
┌─────────┐ ┌────────────┐
│ Filter │ ─────► │ Transfer │
│ *.csv │ │ Condition │
└─────────┘ └─────┬──────┘
▼
Target
Detection conditions can combine the following criteria.
| Condition | Use |
|---|---|
| Create Event | Transfer when a new file is created |
| Modify Event | Reprocess when an existing file is modified |
| File Name | Select files that match a specific naming rule |
| Extension | Transfer only specified file types |
| File Path | Process only files in a specific subfolder |
| Processing State | Prevent duplicate execution based on previous processing |
For example, you can configure the system to transfer only .csv files created in /export/ to another system.
Transfer Connection
Connect detected files to the configured Target and follow-up tasks
After setting the detection conditions, connect the Target that should receive files detected by Hot Folder.
Files can be transferred to a designated location on a server, NAS, cloud storage, or another business system.
┌──► Server
│
Hot Folder ──► Flow ─┼──► NAS
│
└──► Cloud Storage
You can also branch files detected by one Hot Folder to multiple environments or start the next task after the transfer completes.
Hot Folder
│
▼
File Transfer
│
├──────────► Backup Storage
│
└──────────► Processing Server
│
▼
Next Workflow
This supports not only automatic transfer, but a complete workflow from file detection → target transfer → follow-up processing.
Run Management
Review automatically generated Runs and per-file processing results
When a file change detected by Hot Folder starts a transfer job, you can review the execution history in Runs.
In environments where multiple files are created sequentially, execution results show when each file was detected and how far processing progressed.
| Item | Details |
|---|---|
| Source | Device connected to the Hot Folder |
| Source Path | Folder where the file was detected |
| File Event | File creation or modification |
| Target | Destination environment receiving the file |
| Total Files | Number of processed files |
| Status | Current execution status |
| Started | Automatic execution start time |
| Completed | Transfer completion time |
Selecting a specific job lets you review the detected files and transfer results in detail.
Exception Handling
Review files that were not detected or failed to transfer, then reprocess them
Even in an automatic transfer environment, additional review may be required if the file-creation path changes or there is a problem with access permissions or Target connectivity.
In these cases, review the Run details to identify where the issue occurred, adjust the necessary settings, and rerun the job.
Needs Review
│
▼
┌────────────┐
│ Run Details│
└─────┬──────┘
│
┌─────────┼─────────┐
▼ ▼ ▼
Source Conditions Target
Check Check Check
│ │ │
└─────────┼─────────┘
▼
Adjust Environment
Adjust Environment
▼
Retry
│
▼
Review Result Again
When a problem occurs, review the following items together.
| Item | Details | Response |
|---|---|---|
| Source Connection | Device and folder access status | Review connection status |
| Detection Path | Configured Hot Folder path | Adjust path settings |
| File Conditions | Name, extension, and event conditions | Review detection criteria |
| File State | Whether creation or modification completed | Review file state |
| Target Connection | Target system access status | Review connection environment |
| Execution History | Run and per-file processing results | Rerun the required operation |
This lets you automatically detect recurring file changes and operate the full flow from file creation or modification → condition check → automatic transfer → target delivery → execution result management.