Create FTP directory
Description
Creates a directory on an FTP/SFTP server and returns it. Missing parent directories are created too, and a directory that already exists succeeds and is returned, so this is safe to run on every execution. Use it to prepare a destination before Write FTP file when the write itself should not create directories. Branches on success/error.
When to use
Use Create FTP directory when a pipeline needs a directory to exist on an FTP/SFTP server. Like Find FTP files, Get FTP file, and Write FTP file, it is addressed by Credentials and a Path rather than by a file object — the directory does not exist yet, so there is nothing to wire in.
Creating a directory that is already there is not an error: the node takes
the Success pin and returns the existing directory, so it is safe to run on
every execution rather than guarded behind a check. Missing parent levels
are created too, so /exports/2026/09 needs one node, not three.
Write FTP file has its own Create directories option, which covers the common case of writing into a path that may not exist yet. Reach for this node instead when the directory has to exist independently of any file — preparing a destination up front, creating a folder another system will drop files into, or keeping directory creation as its own explicit, separately branchable step.
Pins
Input pins
| Pin | Type | Default | Notes |
|---|---|---|---|
| Credentials | FTP credentials | — | FTP credentials produced by an FTP credentials node. |
| Path | string | — | Path of the directory to create. Every missing level is created, so a nested path needs only this one node. |
Output pins
| Pin | Type | Notes |
|---|---|---|
| Directory | FTP file | The directory, whether it was just created or already there. Break it to read its path, or wire it into Move FTP file to rename it. |
Execution pins
| Pin | Direction |
|---|---|
| In | Input |
| Success | Output |
| Error | Output |
Example
Land a nightly export in a dated folder. Wire FTP username/password
credentials into Create FTP directory with Path /exports/2026/09, then on
Success wire the same credentials plus your content stream into Write FTP
file with Path /exports/2026/09/orders.csv. Because the create is
idempotent, the same pipeline runs unchanged every night — the first run of
a month creates the folder, the rest find it already there.
Wire the Error pin to a Log message so a permissions problem on the server is reported clearly, rather than surfacing later as a confusing write failure.