Using the FTP App in OttoKit

Managing files on your server shouldn’t feel like a chore. With the FTP Core App in OttoKit, you can move, create, and organize files as easily as dragging and dropping them on your computer — except it’s automated, repeatable, and built right into your workflows.

Whether you’re uploading critical reports every night, fetching fresh data for processing, or keeping directories tidy, the FTP Core App puts the power of FTP, FTPS, and SFTP directly at your fingertips.

From creating secure folders to bulk uploads, scheduled downloads, or running file checks, this app connects your server to your automation without leaving OttoKit.

Understanding FTP, FTPS, and SFTP

Before you start, let’s quickly break down what these three options mean so you can choose the right one:

• FTP (File Transfer Protocol)
  The classic way to transfer files between your computer and a server. It’s quick and works almost everywhere, but it sends information (including passwords) in plain text, so it’s best for trusted, internal networks.
• FTPS (FTP Secure)
  An upgraded version of FTP that uses SSL/TLS encryption. Your usernames, passwords, and files are protected during transfer, making FTPS a safer choice for public or less secure networks.
• SFTP (SSH File Transfer Protocol)
  A completely different protocol that runs over SSH (Secure Shell). Every piece of data, including commands, is encrypted, making SFTP the most secure option for sensitive file operations.

Tip: If security is your top priority, use SFTP. If you need compatibility with older FTP setups but want encryption, go for FTPS.

A Quick Word on Permissions

When creating directories, you’ll see numbers like 700, 750, or 755. These are UNIX-style permission codes that define who can read, write, or execute files in a directory.

Example:

• 700 – Only you (the owner) can access the folder.
• 755 – Anyone can view files, but only you can make changes.
• 775 – You and your group can make changes; others can only view.

Choosing the right permissions helps keep your files both accessible and secure.

Creating a Connection

Before you can run any actions, you’ll need to connect OttoKit to your server.

To create a connection:

1. Go to OttoKit > Apps > Create a connection.
2. In the search bar, type FTP and select it.

Fill in these fields:

1. Title – A friendly name for your connection.
2. Protocol – Choose FTP, FTPS, or SFTP.
3. Host – Your server hostname or IP.
   Example: ftp.example.com or 192.168.1.1
4. Port – Default is 21 for FTP/FTPS, and 22 for SFTP.
5. Username – Your server login username.
6. Password – Your server login password.
7. Passive Mode – Yes or No.
   • Use Passive Mode for FTP/FTPS when connecting through firewalls.
   • Not applicable for SFTP.
8. If you are unsure about any detail, you can confirm with your website host.

Actions in the FTP Core App

1. Create a Directory

Use this action to make a new folder on your server.

To create a directory:

1. In your workflow, click Add Step.
2. In the app search bar, type FTP and select it.
3. From the list of available actions, select Create Directory.
4. Under Choose Connection, select the FTP connection you created earlier.
5. Click Continue – this will open the Configure tab.
6. Fill in the fields:
   • Directory Path – Enter the full path where the folder should be created. Example: /public_html/new-folder
   • Create Parent Directories – Yes or No.
   • Permissions – Select 700, 750, 755, or 775.
7. Click Continue – this will open the Test Step tab.
8. Click Test to run the action and verify it works.
9. If the test is successful, click Save.

2. Upload a File

Send a file from your workflow to your server.

To upload a file:

1. In your workflow, click Add Step.
2. In the app search bar, type FTP and select it.
3. From the list of available actions, select Upload File.
4. Under Choose Connection, select your existing FTP connection.
5. Click Continue to go to the Configure tab.
6. Fill in the fields:
   • Remote File Path* – Full path and filename where the file should be saved. Example: /public_html/images/photo.jpg
   • (Optional – click “Show Optional Fields”):
     • File Content – Raw file content.
     • File URL – A direct link to fetch the file from.
     • Content Type – Choose Text/String or Base64.
     • Transfer Mode – Auto-detect, ASCII, or Binary.
7. Click Continue to move to the Test Step tab.
8. Click Test to upload the file and confirm the action works.
9. If successful, click Save.

3. Download a File

Retrieve a file from your server.

To download a file:

1. In your workflow, click Add Step.
2. Search for FTP and select it.
3. From the action list, select Download File.
4. Under Choose Connection, pick your saved FTP connection.
5. Click Continue to open the Configure tab.
6. Fill in the fields:
   • Remote File Path* – Path to the file to be downloaded. Example: /public_html/reports/data.csv
   • Transfer Mode – Auto-detect, ASCII, or Binary.
7. Click Continue to go to Test Step.
8. Click Test – this will return a download URL for the file.
9. If the download is successful, click Save.

4. List Files

View the contents of a directory on your server.

To list files:

1. In your workflow, click Add Step.
2. Search for FTP and select it.
3. From the list of actions, choose List Files.
4. Under Choose Connection, select your FTP connection.
5. Click Continue to go to the Configure tab.
6. Fill in the fields:
   • Directory Path – The directory to scan. Example: /public_html/uploads
   • List Type – All, Files only, or Directories only.
   • Include Details – Yes or No.
7. Click Continue to go to Test Step.
8. Click Test to verify that the file list appears.
9. If the results are correct, click Save.

5. Delete File

Remove a file from your server.

To delete a file:

1. In your workflow, click Add Step.
2. Search for FTP and select it.
3. From the action options, choose Delete File.
4. Under Choose Connection, select your existing FTP connection.
5. Click Continue to go to Configure.
6. Fill in the fields:
   • Directory Path* – Full path of the file to delete. Example: /public_html/images/old-logo.png
7. Click Continue to move to Test Step.
8. Click Test to confirm the file is deleted.
9. If successful, click Save.

Best Practices

• Test connections before running live workflows.
• Use Passive Mode for FTP/FTPS behind firewalls.
• Choose Binary Transfer Mode for large files to prevent corruption.
• Set permissions carefully to balance access and security.

That’s All

With the FTP Core App in OttoKit, managing server files becomes effortless and automated. From creating secure directories to uploading, downloading, listing, or deleting files, everything can now run seamlessly inside your workflows without relying on external tools.

Whether you’re handling nightly report uploads, scheduled data fetches, or simply keeping your directories organized, OttoKit ensures your file operations are secure, reliable, and repeatable.

Start setting up your FTP workflows today and let OttoKit handle the heavy lifting — so you can focus on what matters most.