Automation library · Alerts and monitoring

Automated FTP file migration

Started by a clock, and works across Email and FTP. 9 steps: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 3Service 5

The steps in the order they run, from what starts it.

  1. 1Daily Schedule (2 AM)Schedule triggerStarts it
  2. 2List Files - Source FTPFtpService
  3. 3Filter FilesFilterLogic
  4. 4Download FileFtpService
  5. 5Upload to DestinationFtpService
  6. 6Upload Success?FilterLogic
  7. 7Delete Source FileFtpService
  8. 8Log SuccessSetLogic
  9. 9Send Email Success AlertEmail SendService

How it's built

Starts on
A clock
Steps
9
Size
Medium: a working afternoon
Connects to
Email, FTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email and FTP accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.