Watched Folders
Trigger automations when new or modified files appear on your server.
How it works
Set up a watched folder on any connection. PushFTP checks the folder at your chosen interval (every 1–1440 minutes) and fires a webhook whenever a new file appears — or when an existing file is modified.
Files that are already in the folder when you create the watch are not reported; only files that arrive afterwards are. The exception is a watch that copies to another connection, which also transfers the files already waiting.
This is perfect for triggering Zapier, Make, or n8n workflows when a partner drops or updates a file on your SFTP server — no polling logic needed on your end.
Setup
/incoming).Webhook payload
When a new or modified file is detected, PushFTP POSTs this JSON to your webhook URL. The event field is either new_file or modified_file:
{
"event": "new_file",
"connection": {
"id": "k6J2ilVY...",
"name": "Production SFTP",
"type": "sftp"
},
"file": {
"name": "report-march.csv",
"path": "/incoming/report-march.csv",
"size": 45678,
"modifiedAt": "2026-03-31T14:00:00.000Z"
},
"watchedFolder": {
"id": "wf_abc123",
"path": "/incoming"
},
"timestamp": "2026-03-31T14:01:00.000Z"
}How detection works
- • PushFTP connects to your server at each check interval and lists the folder contents.
- • It compares the current file list to the previous check and identifies new files.
- • If "detect modified" is enabled, it also triggers when a file's size or modification date changes (e.g. a file is overwritten in place).
- • Only files trigger webhooks — subdirectories are ignored.
- • Each file fires a separate webhook call, so you can process them individually.
- • The
eventfield tells you whether it's anew_fileormodified_file. - • Webhooks are retried up to 3 times with exponential backoff (1s, 2s, 4s) if your endpoint is temporarily down.
- • If your endpoint still answers with an error (any status outside 2xx), the file is logged as a failed transfer, which doesn't count toward your monthly transfers, and you get an email. It isn't sent again unless the file changes and "detect modified" is on.
Use with Zapier
With the PushFTP Zapier integration you don't need a webhook URL: use the New File Detected trigger. Turning the Zap on sets up the watched folder for you, and PushFTP sends each new file to Zapier as soon as it's detected. See the Zapier setup guide.
Tips
- • Check interval: 5 minutes is a good default. Set to 1 for near-real-time detection.
- • Large folders: If a folder has hundreds of files, only new files since the last check trigger webhooks.
- • Multiple folders: You can watch multiple folders on the same connection — just add more watched folders.
- • Combine with download: Use the webhook to trigger a Zap that calls the PushFTP Download API to fetch the new file's content.
- • Free plan: each file a watch picks up counts as one of your monthly transfers. When they're used up, new files are held, not lost: they go out at the first check after the monthly reset, or straight away after you upgrade.
- • Detect modified: some servers rewrite the date of every file in a folder when a new one arrives. With "detect modified" on, that sends all of them again; leave it off unless files really are overwritten in place.