FTP uses an FTP credential; SFTP uses an SSH credential. Check remote paths and permissions before writing or deleting. Triggers poll files after publishing; interval and filters determine detected events.
Technical type : ftp. Runtime : nodulz.
Credentials and prerequisites
FTP / FTPS (ftp / user_password). FTP server with username and password. Explicit TLS enabled by default.
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Transfer and manage files over FTP or FTPS.
Usage and specifics
FTP uses an FTP credential; SFTP uses an SSH credential. Check remote paths and permissions before writing or deleting. Triggers poll files after publishing; interval and filters determine detected events.
Technical type :
ftp. Runtime :nodulz.Credentials and prerequisites
ftp/user_password). FTP server with username and password. Explicit TLS enabled by default.Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
credentialIdstring""operationenum"list"list,download,upload,rename,delete,mkdir,rmdirpathstring"."destinationstring""contentstring""encodingenum"utf8"utf8,base64Configuration help
operationOperation
destinationDestination path
encodingEncoding
contentContent
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "credentialId": "", "operation": "list", "path": ".", "destination": "", "content": "", "encoding": "utf8" }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.