New SFTP To Go Feature: Native File Automations

Native file automations are here, and it’s fair to say we’re hyped about what you can do with them!

File system events and scheduling can now drive automated workflows directly inside SFTP To Go to move, copy, delete, encrypt, or decrypt files as they arrive, string multiple actions together, and trigger a webhook when everything’s done.

It’s a powerful new addition to SFTP To Go that brings more of your file processing into one place, with plenty of possibilities for building smarter, more efficient workflows.

Automate file workflows directly in SFTP To Go

We’ve supported automation around SFTP To Go for a long time through APIs, webhooks, scripts, and external tools.

Now, more of the file processing itself can happen directly inside SFTP To Go.

With native File Automations, you can create scheduled or event-driven workflows that take care of recurring file operations as files arrive, including workflows with several steps performed in sequence. Instead of relying on a separate script to handle each operation, the processing can happen right where your files already are!

Build multi-step workflows around incoming files

Choose the actions you need and combine them into a workflow that runs them in order.

You can:

Move files
Copy files
Delete files
Encrypt files with PGP
Decrypt PGP-encrypted files
Create file or folder
Add a delay
Send notifications to Slack, Microsoft Teams and email
Trigger a webhook

Such actions can be chained together, with each step able to pick up from the one before it so you don’t have to keep defining the same source throughout the workflow.

For example, an incoming file could be decrypted and moved to the right folder, or encrypted and copied to another location before a webhook lets a connected system know that processing is complete.

This gives you plenty of room to build anything from a short two-step process to a longer workflow with several actions running in sequence.

Add automated PGP encryption and decryption

PGP can now become part of the automated process rather than a separate step before or after it.

This is useful for workflows where files need additional file-level protection before they’re moved, shared, or processed, as well as incoming PGP-encrypted files that need to be decrypted before the next action can take place.

Importantly, the encryption keys used by these automations are themselves stored encrypted in a dedicated secrets store, separate from the automations that reference them. Access is restricted to the owning organization and to the operations that need the key material.

It brings encryption and file processing together in the same workflow, reducing the need for separate manual processes or scripts.

Trigger connected systems and send notifications

File Automations don’t stop at processing files. You can also add actions that send a webhook request or notify people through Slack, Microsoft Teams, or email.

That means a workflow can process the file first, then send the notification or trigger the connected system at the right point in the sequence.

For example:

File created → decrypt → move → webhook

File downloaded → copy → Teams notification

File deleted → email notification

or, for scheduled workflows:

Scheduled trigger → encrypt → copy → webhook

If you’re already using SFTP To Go webhooks, there’s also an option to migrate them to Automations, making it easier to bring existing event-driven processes into the new workflow builder.

For more on webhook notifications and how they work in SFTP To Go, see our webhook documentation.

Keep track of your automations

File Automations also include workflow history, giving you visibility into how your automated processes are running and what happened when something didn’t go as planned.

You can review workflow activity, identify failed actions, and see how retries are handled without having to trace the process through an external script.

For the finer details on workflow history, failures, retries, and configuration, head to our File Automations documentation.

Native automations alongside APIs and webhooks

Native File Automations add a new option to SFTP To Go’s existing automation toolkit, including webhooks triggers, email notifications, and management APIs.

You can use File Automations for file operations that should happen inside SFTP To Go, while APIs and webhooks remain available when you need to connect SFTP To Go with external applications, services, and processes.

That gives you more flexibility to decide where each part of a workflow belongs.

Ready to get started?

These features are currently in beta and will be available on an opt-in basis while we continue to refine them ahead of the wider rollout. If you’d like to start using them during the beta period, you can opt in and get access before they become available to everyone.

Create a File Automation, set up a schedule or choose what should trigger it, add the file actions you need in the order they should run, and decide whether the workflow should finish by triggering a webhook.

The detailed setup and configuration options are covered in our File Automations documentation.

Our recent features

We’ve been rolling out plenty of new SFTP To Go features and updates. Catch up on the latest releases, from newest to oldest:

We value your feedback

File Automations open up a lot of new possibilities for how files can be handled inside SFTP To Go, and we’d like to hear how you’re using them.

If you have feedback, questions, or ideas for future automation actions, send us a message through the in-app chat. We’re always interested in hearing what would make your workflows work better.