Output

FTP / SFTP

Upload to server

Uploads the finished result to a file server over FTP or SFTP, common when a partner or an older system expects files dropped into a folder.

How it works

Plenty of established systems, especially at banks, insurers, logistics partners, and legacy back offices, exchange data the old reliable way: by dropping files into a folder on a server. This node does exactly that, connecting to the FTP or SFTP address you give it and uploading each job's result into the folder they told you to use.

SFTP is the secure, encrypted version and is what most partners require today. FTP is the plainer, older variant. dojobase supports both, so you match whatever the receiving party specified.

You supply the server address, the login, and the destination folder. When a partner says 'just SFTP us the file every time,' this is the step that satisfies that request without anyone logging in manually.

Common use cases

Real situations where this node earns its place in a flow.

Deliver to an SFTP endpoint

Upload a file to a partner's server that expects FTP or SFTP drops.

Send to a trading partner

Push documents to a server-based exchange in an EDI-style flow.

Post nightly files

Combine with a schedule to deliver a batch to a server each night.

FTP / SFTP in a workflow

A simple example of where this node sits in a flow.

What you set up

Enter the server host address, port, and whether it is FTP or SFTP.
Provide the username and password (or key) the partner issued you.
Set the destination folder path and the file name to upload as (job values can be included in the name).

Common questions

What's the difference between FTP and SFTP here?

SFTP encrypts the connection and the file in transit; plain FTP does not. Most partners now require SFTP. Use whichever your recipient specified in their setup instructions.

Can I control the folder and file name?

Yes. You set the destination folder and the upload file name, and you can embed job values (like a date or ID) so files sort cleanly on the server.

Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.

Field	Type	Default	What it controls
`host`req	string	—	FTP/SFTP server hostname.
`port`	number	—	Server port; a protocol default is used when unset.
`username`	string	—	Login username.
`password`	string (secret)	—	Login password; resolved from the org secret vault.
`targetDirectory`	string	`/`	Remote directory to upload into.
`filenameTemplate`	string	—	Uploaded filename template; a default is used when blank.
`maxAttempts`	number	—	Max delivery attempts before giving up.
`backoffSeconds`	number	—	Base backoff in seconds between retry attempts.

hostreq
FTP/SFTP server hostname.
Type: string
port
Server port; a protocol default is used when unset.
Type: number
username
Login username.
Type: string
password
Login password; resolved from the org secret vault.
Type: string (secret)
targetDirectory
Remote directory to upload into.
Type: stringDefault: /
filenameTemplate
Uploaded filename template; a default is used when blank.
Type: string
maxAttempts
Max delivery attempts before giving up.
Type: number
backoffSeconds
Base backoff in seconds between retry attempts.
Type: number

How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.

{
  "id": "ftp-out",
  "type": "card",
  "position": {
    "x": 160,
    "y": 120
  },
  "data": {
    "type": "ftp-out",
    "kind": "output",
    "title": "FTP / SFTP",
    "subtitle": "Upload to server",
    "config": {
      "host": "",
      "port": "0",
      "username": "",
      "password": "",
      "targetDirectory": "/",
      "filenameTemplate": "",
      "maxAttempts": "0",
      "backoffSeconds": "0"
    }
  }
}