How to connect an SFTP or FTP server
This tutorial shows you how to give Dattos access to an SFTP or FTP server so that processes can retrieve input files and deliver exported files to it. This is the most common way to receive bank statements, acquirer files, and reports from systems that generate files. For an overview of the integration, see File repositories: which ones Dattos connects to and how to set them up.
Which type to choose
Credential type | When to use |
|---|---|
SFTP - Password | The SFTP server authenticates with a username and password |
SFTP - SSH Key | The SFTP server authenticates with an SSH key. This is the most secure option and the one required by most banks |
FTP | Only when the server does not offer SFTP |
FTP is not encrypted. Usernames, passwords, and file contents are transferred without protection. Whenever the server offers SFTP, use SFTP instead.
What you need
A server accessible over the internet. Dattos does not connect to internal network addresses (for example,
10.x.x.x,172.16.x.xto172.31.x.x,192.168.x.x),localhost, or servers that only exist inside your company's VPN.A firewall configured to allow Dattos. If the server only accepts connections from known addresses, ask Dattos Support for the addresses that need to be allowed.
A dedicated user for Dattos, with permission to list, read, write, rename, and move files, and create folders in the folders it will use. Dattos creates the control subfolders
.processing,.processed, and.errorinside the source folder.The folders already created on the server.
1. Prepare the SSH key (SFTP - SSH Key only)
Skip this step if the server uses a password.
Generate a key pair (for example, with
ssh-keygenor PuTTYgen). You can protect the key with a passphrase.Send the public key to the SFTP server administrator so they can authorize the Dattos user.
Keep the private key safe: this is the key you will send to Dattos by pasting it as text.
Dattos accepts RSA, ECDSA, or Ed25519 keys in OpenSSH (the text starts with -----BEGIN OPENSSH PRIVATE KEY-----), PEM (-----BEGIN RSA PRIVATE KEY----- or -----BEGIN PRIVATE KEY-----), or PuTTY (.ppk, opened in a text editor) formats. DSA keys are not accepted.
If the bank or partner generates the key and sends it to you, check that it is in one of these formats.
2. Add the credential in Dattos
Click the gear icon and open General › Credentials.
Click + New credential and, on the Storage tab, choose SFTP - Password, SFTP - SSH Key, or FTP.
Fill in the fields:
Field | What to enter | Types |
|---|---|---|
Credential name | A name that identifies the server, such as "SFTP Bank X - statements" | All |
Host / URL | The server address only (for example, | All |
Port |
| All |
Username | The user created for Dattos | All |
Password | The user's password | SFTP - Password and FTP |
Private Key | The entire text of the private key file, from the first line to the last | SFTP - SSH Key |
Key Passphrase | The key's passphrase, if you created one. Leave blank if the key has no passphrase | SFTP - SSH Key |
Remote Path | Optional. The folder from which Dattos lists folders, for example | All |
Privacy profiles | Who can use this credential in processes | All |
Click Save.
3. Test the connection (SFTP only)
After saving, open the credential again and click Test connection.
The test confirms that the server responds at the specified address and port. It does not check the username, password, or key: a successful test means that Dattos can reach the server, not that the login will work. FTP does not have a Test connection button. For both types, the full confirmation comes in the next step.
4. Check and connect the server to a process
Open a Turbo AI process with the flow published, and go to Source Directory.
Click Edit for the desired source, then click Add destination.
Under Storage Integration, choose the credential you created.
If the server folders appear under Import Folders, the login and read permissions are correct. Choose the folder and save.
For the complete step-by-step instructions, including output setup, see Integrating with file repositories: source and output directories.
Tip: Use FileZilla to view and test folders
Dattos displays the server folders, but not the files. To check whether a file has arrived, whether it was moved to .processed or .error, or whether an export was delivered, use a file transfer program such as the free FileZilla Client for Windows, macOS, and Linux.
FileZilla also helps you test the login before adding the credential, which Dattos's Test connection feature does not do:
Open File › Site Manager and click New site.
Under Protocol, choose SFTP – SSH File Transfer Protocol (or the FTP option).
Fill in Host and Port with the same values you plan to use in Dattos.
Under Logon Type, choose Normal for a username and password, or Key file for an SSH key. Enter the Username created for Dattos and, for a key, click Browse and select the private key file (on Windows, change the filter to All files if the key does not appear). If the key is not in a format FileZilla uses, it will offer to convert it and save a converted copy; accept. In Dattos, continue to paste the original key.
Click Connect.
If FileZilla logs in with this user and displays the folders, the access details are correct. Keep in mind that FileZilla connects from your company's network: a server that responds from inside the company may still be blocked for Dattos if the firewall does not allow access from outside.
Control subfolders start with a dot (.processing, .processed, .error), so many servers treat them as hidden. If they do not appear in FileZilla, open the Server menu and enable the option to force hidden files to be shown (in English, Force showing hidden files).
Common issues
What you see | Likely cause |
|---|---|
Test connection times out | The server firewall is blocking Dattos, the port is incorrect, or the server is down |
Error during the test or while loading folders, even though the server is up | The Host / URL points to an internal network address or was entered with |
Test connection succeeds, but the folders do not load | The username, password, or key is incorrect, or the public key has not been authorized on the server |
The folders appear, but the run ends with an error while moving the file | The user does not have permission to rename files or create folders |
The folder list is empty or incomplete | The Remote Path points to a different folder, or the user does not have permission to list the expected folders |