Create FTP Directory
Create one exact agent-selected remote directory with FTP MKD.
Protocol connection for stateless remote browsing, recursive agent-selected transfers, and exact remote path management.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
7 matching actions
Create one exact agent-selected remote directory with FTP MKD.
Delete one exact remote directory, either with one RMD or with an agent-selected recursive post-order deletion.
Delete one exact agent-selected remote file with FTP DELE.
Download one or more remote FTP files or directories to exact agent-selected local destinations with recursive tree preservation.
List one remote FTP directory without downloading its files; returned child paths can be reused in later actions.
Ask the FTP server to rename or move one exact remote file or directory path with RNFR followed by RNTO.
Upload one or more agent-selected local files or directories; directories recurse automatically and preserve their relative tree.
Direct answer
People continue using FTP / Explicit FTPS as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 7 FTP / Explicit FTPS actions across File Transfer. The exact actions used depend on the workflow and approval rules.
No. FTP / Explicit FTPS remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.