Skip to main content

Build a File-Driven Integration

TimeUnder 10 minutes
What you'll buildA file integration that adds an onModify handler to track file changes and uses printInfo to log file modification events.

File integrations are ideal for batch uploads, scheduled file processing, and ETL workflows triggered by files appearing in a folder or FTP server.

Prerequisites​

A working WSO2 Integrator environment.

You'll also need a file at the listener path to watch. Create one if you don't have one:

echo "test" > /tmp/testfile.txt

Step 1: Create the integration​

  1. On the project home page, click Create on Cloud.

    WSO2 Cloud project home showing the Create on Cloud optionWSO2 Cloud project home showing the Create on Cloud option
  2. The WSO2 Integrator cloud editor opens in your browser. Add an artifact to your integration, then deploy it to WSO2 Cloud from the Deploy to WSO2 Cloud panel on the right.

    WSO2 Integrator cloud editor landing page showing an empty integration and the Deploy to WSO2 Cloud panelWSO2 Integrator cloud editor landing page showing an empty integration and the Deploy to WSO2 Cloud panel

Step 2: Add a file integration artifact​

  1. Select your integration from the project overview canvas.
  2. In the design view, select + Add Artifact.
  3. Select Local Files under File Integration.
  4. Set Path to /tmp (macOS/Linux) or C:\tmp (Windows). Select Create.
Create Local Files form with Path set to /tmp and Recursive set to FalseCreate Local Files form with Path set to /tmp and Recursive set to False

Step 3: Add onModify event handler​

  1. In the service designer view, select + Add Handler.
  2. Select onModify.
Select Handler to Add panel showing onCreate, onDelete, and onModify optionsSelect Handler to Add panel showing onCreate, onDelete, and onModify options

Step 4: Add file tracking logic​

  1. Select + in the flow diagram.
  2. Search for printInfo and select printInfo.
  3. Set Msg to File modified and select Save.
Flow Designer showing the onModify handler with printInfo configured to log File modifiedFlow Designer showing the onModify handler with printInfo configured to log File modified

Step 5: Run and test​

  1. Select Run in the toolbar.

  2. Run the modify command in your terminal to trigger the handler:

    echo "modify" > /tmp/testfile.txt
  3. Confirm the run terminal shows the log line File modified.

Flow designer showing the integration running with log:printInfo emitting File modifiedFlow designer showing the integration running with log:printInfo emitting File modified

Source code​

View the generated Ballerina code

The steps above generate the following complete, runnable Ballerina program:

Windows

Change the listener path from "/tmp" to "C:\\tmp" (backslash escaped) before running the program.

import ballerina/file;
import ballerina/log;

listener file:Listener fileListener = new (path = "/tmp", recursive = false);

service file:Service on fileListener {
remote function onModify(file:FileEvent event) returns error? {
do {
log:printInfo("File modified");
} on fail error err {
// handle error
return error("unhandled error", err);
}
}

}

Learn more​

  • Local files — Full Local Files listener reference (events, recursive watching, file handlers)
  • FTP/SFTP — Watch and process files on remote FTP or SFTP servers
  • Streaming large files — Process large files without loading them fully into memory
  • CSV fault tolerance — Handle errors and partial failures when processing CSV files