Node reference

FTP List for Joomla and WordPress

Lists files in a remote FTP directory when the flow runs. Use as the first step in poll-and-process pipelines that ingest partner file drops.

Overview

Lists files in a remote FTP directory when the flow runs. Use as the first step in poll-and-process pipelines that ingest partner file drops.

When the flow reaches this step, JOrchestrator executes FTP List against your linked site or an external integration, using the field values you set on General and Design. Downstream steps can read the output payload fields defined for this node.

Why use this node

FTP List is a action step in the Connectors › FTP group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add FTP List to a flow:

  • Poll an FTP folder for new files to drive an Iterator loop
  • Inventory remote files before selective download or delete steps
  • Verify expected filenames exist before triggering import flows

Example workflows

Common patterns on the canvas:

  1. Trigger or Webhook → upstream steps → FTP ListSend Email or CMS update
  2. Scheduled triggerFTP ListDebug (while testing) → production action

How to set it up

Enter host, credentials, and optional remote directory on the Design tab.

Good to know

Returns files[] with name, type, size, and date for each entry — wire an Iterator to process each file.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-specific configuration fields

System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

Property keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo
_payloadFieldsAvailable Fieldspayload-panelNo

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNoNode label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
hostHostpayload-textYesftp.example.com
portPortpayload-textNo21 Default FTP port is 21.
usernameUsernamepayload-textYesUsername or {{secrets.ftp_user}}
passwordPasswordsecret-textYesPassword or {{secrets.ftp_pass}}
timeoutSecondsTimeout (seconds)number (default: 30)No
passiveModePassive modetoggle (default: true)NoRecommended for most firewalls. Data transfers use passive mode by default.
remotePathRemote directorypayload-textNo. or /uploads/ Directory to list. Use . for the login directory.
maxFilesMax filesselect (100 | 500 | 1000 | 2500 | 5000 | 10000; default: 1000)No

CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as {{ftp_list.success}}.

Field keyTypeDescription
successbooleanWhether the operation completed successfully.
hoststringText value from this node's output.
remotePathstringText value from this node's output.
countnumberNumber of items in the result set.
filesarrayArray of file entries with name, type, size, and date.
namesarrayFlat array of file names in the directory.
messagestringHuman-readable status, error, or result summary.

Validation rules

  • Host (host) must be filled before the flow can be saved.
  • Username (username) must be filled before the flow can be saved.
  • Password (password) must be filled before the flow can be saved.