An FTP / SFTP connection lets the FTP / SFTP steps — Upload a file, Download a file, List a folder, Delete a file, Rename or move a file and Create a folder — and the New file in a folder trigger work with a file server: a supplier's SFTP drop, your hosting account, or a server of your own.

Who can do this

  • Workspace Admins and Editors, on every plan.

Before you start

  • The server's address, the protocol and a user. Your host or the server's owner gives these. SFTP (over SSH) and FTPS (FTP with TLS) keep files and the password private; plain FTP sends both unencrypted.
  • A password, or a private key for SFTP. For a key, have the whole private key ready — the text from -----BEGIN to -----END — and its passphrase if it has one.
  • Reachable from the internet. The server must have a public address, and its firewall must let Bizomate in (below). A server on a private network or behind a VPN cannot be reached.

The addresses Bizomate connects from

If the server only lets in addresses you list, add all of these. Bizomate connects from one of them, and which one can change without notice, so allow every one:

20.244.77.107, 98.70.233.34, 98.70.238.182, 4.187.192.56, 4.187.192.83, 4.187.202.192, 4.247.208.118, 4.188.89.53, 20.235.194.47, 135.13.177.151, 135.13.180.237, 4.224.138.26, 4.224.139.74, 4.188.89.72, 4.247.208.154, 4.224.71.1, 4.188.115.70, 4.187.190.117, 20.219.174.118, 20.204.214.217, 4.247.214.195, 4.247.236.85, 4.247.215.225, 4.224.71.224, 4.224.115.37, 4.224.115.87, 4.187.214.53, 4.187.204.15, 20.204.211.52, 20.204.214.68, 20.192.171.20

These are the outgoing addresses of Bizomate's servers in Azure Central India (as of 2 October 2026). If they change, this article is updated.

Steps

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Cloud Storage, select FTP / SFTP. The window notes: "Fill in a password or a private key. Testing keeps the SFTP server's key, so a server that later shows another key is refused."
  3. In Connection name, type a name — for example Northwind supplier drop.
  4. In Protocol, choose SFTP, FTPS or FTP (unencrypted).
  5. In Host, type the server's address — files.consulace.com.
  6. Port — empty for 22 (SFTP) or 21 (FTPS and FTP). Type 990 for a server that uses FTPS from the first byte (implicit FTPS).
  7. In Username, type the user.
  8. In Password, type its password — or, for SFTP, paste the whole key into Private key and, if it has one, its Key passphrase.
  9. Leave Test the connection before saving ticked, then select Save connection.

What happens next

  • The connection appears under Cloud Storage. In the step picker its steps are under Developer.
  • Test signs in and lists the top folder, answering for example "Reached files.consulace.com as bizomate · SFTP · key SHA256:…". Plain FTP adds "— unencrypted".
  • For SFTP, the test keeps the server's key — the SHA256 fingerprint in that sentence. Every step and check after uses the server only if it shows the same key. If you want to be sure it is your server, compare the fingerprint with the one its owner gives you.

Good to know

  • A changed key stops the connection. If the server later shows another key — a rebuilt server, or someone posing as it — every step fails with "The server's key changed since this connection was saved. If you expected that, test the connection again to accept the new key." Select Test on the connection when you know the change is expected; the test keeps the new key.
  • Saved without testing, an SFTP connection has no key kept, and its steps say so: "Bizomate has not kept this server's key yet. Test the connection once on Connections to keep it."
  • FTP's file transfers go to the server you connected to, never an address the server names, so a server cannot send Bizomate elsewhere.
  • The password, key and passphrase are never shown again. Reconnect to change any field; with Test the connection before saving ticked, the server's key is kept again.

If something goes wrong

What you see Why What to do
"The server refused the username, password or key. Check them on Connections." The sign-in is wrong, or the key is not on the server for that user. Check the user and password, or add the public half of the key to the server.
"The server did not answer. Check the host, port and protocol on Connections, and that its firewall lets Bizomate in." The port or protocol does not match, or the firewall did not let Bizomate in. Check them; allow Bizomate's addresses.
"The private key could not be read: … Paste the whole key — with its BEGIN and END lines — and its passphrase if it has one, on Connections." Part of the key is missing, or the passphrase is wrong. Paste the whole key again, with the right passphrase.
"A private key signs in only over SFTP. …" A key was given for FTPS or FTP. Choose SFTP, or use a password.
"The server's FTPS certificate is not one Bizomate can trust. …" The server's TLS certificate is expired or for another name. Ask the server's host to fix the certificate.
"… is not on the public internet, so workflows cannot reach it." The host is a private address. Use the server's public address.