Automate file‑based integrations without custom schedulers (OIC Gen3 24.10+) File‑based integrations are still extremely common—daily CSV extracts, XML drops from legacy systems, or batch partner feeds over FTP/SFTP. Before Oracle Integration Cloud (OIC) Gen3 24.10, Scheduled integrations External scripts Custom polling logic Gen3 introduced a native File‑Polling trigger and it simplifies everything. In this post, I’ll walk through how to use the new FTP File Polling trigger, when to use it, and what to watch out for. When Should You Use File Polling? Files are small to medium in size You want to trigger immediately on file arrival You don’t need manual file download logic You prefer a low‑code, native OIC pattern Typical use cases: Daily CSV or XML reports Lightweight batch integrations Partner file drops Staging‑based data ingestion What’s New in OIC Gen3 24.10+ Automatically trigger an integration when a file arrives Match files using filename patterns Load file content directly as payload Control archive, delete, or reject behavior Avoid additional adapters or scripts Step‑by‑Step: Configuring File Polling in OIC 1. Verify OIC Version Oracle Integration Cloud Gen3 – 24.10 or later File polling is not available in earlier Gen3 builds. 2. Configure FTP / SFTP Connection Host, port, credentials Source directory permissions Optional archive/reject directories Test the connection before proceeding. 3.Use the File‑Polling Trigger Select the FTP Adapter as the trigger Choose File Polling as the trigger type You’ll configure: Polling frequency (e.g., every 5 minutes) Source directory Filename pattern (e.g., *.csv) Schema type (CSV / XML) Optional sample file upload for schema generation This eliminates the need for a separate file‑server read step. 4. Configure File Handling Behavior 📦 Archive the file This is extremely useful for idempotency and cleanup. 5. Design the Integration Flow Parse file content using the generated schema The file content is already available as the payload—no manual streaming required. 6. Test with a Proof of Concept (POC) Drop a test file matching the pattern Confirm the integration triggers immediately Validate: *File movement (archive/delete) *Payload parsing *Error handling 7. Deploy & Monitor Activate the integration Monitor tracking for file runs Adjust polling frequency or file rules if required