Bring files into a workflow from your own library, an FTP or SFTP server, or Google Drive-then feed them straight into a transform, sync, or export step.
Every workflow needs a starting file. The Data Sources category in the Node Palette gives you three ways to bring one in: Select File for anything already in My Files, FTP/SFTP Import for files sitting on a remote server, and Google Drive Import for files stored in Drive. Once a source node runs, its output is available to the next node in the chain-usually a Transform Template or an export step.
Data Source nodes live in the Node Palette on the left side of the workflow canvas, grouped under their own section.
Node Palette
Drag a node onto the canvas (or click to add)
Data Sources
Select File
Pick a file from My Files
FTP/SFTP Import
Import a file from FTP server
Google Drive Import
Import from Google Drive
A workflow can only have one entry point, so keep a single Data Source node feeding the rest of the chain. Use a Manual Trigger, Schedule, or Webhook node upstream to control when it runs.
Use a file you've already uploaded to My Files as the starting point for the workflow.
If you overwrite or replace the selected file in My Files before the next run, the workflow will pick up the new version automatically.
Pull a file directly from a remote FTP or SFTP server, so the workflow can run against data that lives outside Supabind.
Credentials are stored securely and reused for every run-you won't need to re-enter them unless the server details change.
Import a file straight from a connected Google Drive account without downloading and re-uploading it manually.
Pointing at a folder instead of a single file will pull in the most recently modified file each run-handy for sources that get replaced on a schedule.
If you're having trouble connecting to an FTP/SFTP server, authorizing Google Drive, or picking up the right file, our support team is here to help.
Contact Support