Node reference

FTP Delete for Joomla and WordPress

Deletes a file on a remote FTP server when the flow runs. Use after successful download or import to keep drop zones tidy.

Overview

Deletes a file on a remote FTP server when the flow runs. Use after successful download or import to keep drop zones tidy.

When the flow reaches this step, JOrchestrator executes FTP Delete 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 Delete 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 Delete to a flow:

Remove processed files from a partner FTP drop zone after ingestion
Clean up temporary exports once downstream steps archive them
Enforce retention on nightly scheduled flows over legacy FTP archives

Example workflows

Common patterns on the canvas:

Trigger or Webhook → upstream steps → FTP Delete → Send Email or CMS update
Scheduled trigger → FTP Delete → Debug (while testing) → production action

How to set it up

Enter host, credentials, and remote path on the Design tab.

Good to know

Deletes a single file at the given path — confirm path placeholders resolve correctly in test runs.

Properties panel

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

System (automatic — not edited by the user)

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	—	—

User-configured — General tab

Property key	Label	Type	Required	Visible when	Notes
`label`	Label	`text`	No	—	Node label

User-configured — Design tab

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

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_delete.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.
`message`	string	Human-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.
Remote path (remotePath) must be filled before the flow can be saved.