FTP Upload is a Step (action) in Connectors › FTP. Uploads file content to a remote FTP server.
FTP Upload is a Step (action) in Connectors › FTP. Uploads file content to a remote FTP server.
When the flow reaches this step, JOrchestrator executes FTP Upload 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.
FTP Upload 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 Upload to a flow:
Common patterns on the canvas:
Enter host, credentials, remote path, and body on the Design tab. Use {{placeholders}} for dynamic values.
Returns bytesWritten on success. Use base64 body encoding for binary files.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| General | Canvas label and read-only node ID |
| AI | Optional assistant to help draft settings from plain language |
| Design | Node-specific configuration fields |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
_payloadFields | Available Fields | payload-panel | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
host | Host | payload-text | Yes | — | ftp.example.com |
port | Port | payload-text | No | — | 21 Default FTP port is 21. |
username | Username | payload-text | Yes | — | Username or {{secrets.ftp_user}} |
password | Password | secret-text | Yes | — | Password or {{secrets.ftp_pass}} |
timeoutSeconds | Timeout (seconds) | number (default: 30) | No | — | — |
passiveMode | Passive mode | toggle (default: true) | No | — | Recommended for most firewalls. Data transfers use passive mode by default. |
remotePath | Remote path | payload-text | Yes | — | /path/to/file.txt |
body | Body | textarea | Yes | — | File content or {{node_id.field}} |
contentEncoding | Body encoding | select (text | base64; default: text) | No | — | — |
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.
After this step runs, later nodes can reference these fields using placeholders such as {{ftp_upload.success}}.
| Field key | Type | Description |
|---|---|---|
success | boolean | Whether the operation completed successfully. |
host | string | Text value from this node's output. |
remotePath | string | Text value from this node's output. |
bytesWritten | number | Number of bytes uploaded to the remote server. |
message | string | Human-readable status, error, or result summary. |
host) must be filled before the flow can be saved.username) must be filled before the flow can be saved.password) must be filled before the flow can be saved.remotePath) must be filled before the flow can be saved.body) must be filled before the flow can be saved.Other steps in the same area of the palette:
ftp-delete) — Connectors › FTPftp-download) — Connectors › FTPftp-list) — Connectors › FTP