Fetch from SFTP
Fetch selected files from an SFTP server into a Multi FileFeed.
Fetch from SFTP retrieves one or more files from an SFTP server and brings them into your Multi FileFeed (MFF) as input files. This is one of the most common ways to start an MFF when partners or vendors deliver files by SFTP.
Availability: GA
What it does
- Input: source (no upstream input). This transform starts an MFF branch by connecting directly to an SFTP server.
- Output: one file per selected file on the server, in its original format.
- The transform connects using the configured SFTP account, retrieves the files you select, and passes them downstream unchanged.
When to use it
- A vendor or partner drops files into an SFTP directory on a recurring schedule.
- You currently download files manually from SFTP before uploading them to OneSchema.
- You want to combine SFTP-sourced files with files fetched from other connectors in the same MFF.
How to configure it
In the MFF builder, add a Fetch from SFTP node as a source at the start of your MFF.
Settings
| Setting | Description | Default |
|---|---|---|
| Files | The list of files or file paths on the SFTP server to fetch as input files. | None selected |
| SFTP account | The connected SFTP credential to use for the fetch. | None selected |
Configuration tips
- Use full, exact paths where possible. If the vendor's filename includes a date stamp, check whether your account setup supports pattern matching for the current file.
- Confirm the SFTP account has read access to the directory before saving the node.
Example
Setup
A partner uploads orders_20240501.csv nightly to /inbound/orders/ on their SFTP server.
Output
The MFF receives orders_20240501.csv as an input file, ready for validation and mapping downstream.
Troubleshooting
Connection or authentication errors
- Confirm the SFTP account's credentials and host details are still valid.
- Check whether the server's IP allowlist includes OneSchema's fetch infrastructure.
"File not found" errors
- Confirm the file path is exact and that the vendor hasn't changed their naming convention or folder structure.
See also
Updated 1 day ago
Did this page help you?