Supabind

Data Sources

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.

Overview

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.

Add a Data Source Node

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

Steps

  1. Open or create a workflow.
  2. In the Node Palette, find the Data Sources section.
  3. Drag a node onto the canvas, or click it to drop it in automatically.
  4. Connect it to the next node-typically a Transform Template-by dragging from its connector dot.

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.

Select File

Use a file you've already uploaded to My Files as the starting point for the workflow.

Steps

  1. Add the Select File node to the canvas.
  2. Click the node and choose a file from My Files in the configuration panel.
  3. Save the workflow-the chosen file will be re-read from My Files each time the workflow runs.

If you overwrite or replace the selected file in My Files before the next run, the workflow will pick up the new version automatically.

FTP/SFTP Import

Pull a file directly from a remote FTP or SFTP server, so the workflow can run against data that lives outside Supabind.

Steps

  1. Add the FTP/SFTP Import node to the canvas.
  2. Enter the server host, port, credentials, and the file path to fetch.
  3. Connect the node's output to a Transform Template or export node.

Credentials are stored securely and reused for every run-you won't need to re-enter them unless the server details change.

Google Drive Import

Import a file straight from a connected Google Drive account without downloading and re-uploading it manually.

Steps

  1. Add the Google Drive Import node to the canvas.
  2. Connect your Google account if you haven't already, then browse to the file or folder to import.
  3. Connect the node's output to the next step in your workflow.

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.

Was this article helpful?

Need More Help?

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