# File Input Task
The **File Input Task** is an **event‑based node** used to **start a business process automatically** when a file is detected in a specified repository.\
It is represented by a **rectangular BPMN node**, as shown below.
Unlike regular activities that execute after a process has started, the File Input Task functions as a **process trigger**, initiating a new process instance when matching file conditions are met.
***
### Purpose
The **File Input Task** is used when a business process must begin **automatically based on file arrival**.
It is functionally similar to the **File Read Task**, with one key difference:
> **File Input Task starts the process**\
> ⏭ **File Read Task executes within an already running process**
Typical use cases include:
* Batch processing triggered by file uploads
* Integration with external systems that drop files
* Scheduled or event‑driven data ingestion
* Automated ETL‑style workflows
***
### Supported File Types
The File Input Task supports the following file formats:
* **Excel**
* **Fixed Width**
* **Delimited**
* **XML**
These formats allow structured data files to be used as reliable process triggers.
***
### Supported File Repositories
The File Input Task can monitor files from multiple repositories:
* **File System**
* **FTP**
* **FTPS**
* **Secured FTP (SFTP)**
When a file matching the defined configuration appears in the selected repository, a new instance of the process is created.
***
### File Input Task Configuration Properties
The **File Input Task** uses the **same configuration properties** as the **File Read Task**, including:
* File source configuration
* File type configuration
* Filtering, sorting, and transformation rules
* Duplicate handling
* File movement after processing
* Business Object input/output mapping
This consistency ensures that users do not need to learn a separate configuration model.
***
### Relationship to File Read Task
Although the two nodes serve different roles in the process lifecycle, they share the same configuration structure.
| Node | Role |
| ------------------- | ---------------------------------------- |
| **File Input Task** | Starts a new process when a file arrives |
| **File Read Task** | Reads file data during process execution |
> For detailed configuration options, property definitions, and examples, please refer to:
>
> **File Read Task**\
>
***
### Usage Guidelines
* Use **File Input Task** only at the **start of a process**
* Ensure repositories and credentials are configured correctly
* Avoid duplicate triggers by carefully defining file patterns
* Use Business Object mapping to capture file data at process start
* Combine with Gateways and Activities for downstream logic
***
### Summary
The **File Input Task** enables file‑driven, event‑based process execution in ONEWEB.
Key points:
* Automatically starts a process when a file arrives
* Shares configuration model with File Read Task
* Supports multiple file formats and repositories
* Ideal for batch, integration, and data ingestion workflows
* Acts as a bridge between external file systems and process automation
Correct use of the File Input Task allows you to design **fully automated, event‑driven business processes** that respond directly to real‑world file events.
---
# Agent Instructions: 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:
```
GET https://docs.onewebstack.com/oneweb-platform-th/designer-reference/process-designer/process-designer-component/event/file-input-task.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
