What PushFTP Does
PushFTP is a file transfer relay with a fixed IP address. It sits between your automation tools (Zapier, Make, n8n) and your file servers (SFTP, FTP, S3). Instead of those tools connecting directly — and getting blocked because their IPs rotate — everything routes through PushFTP's single static EU IP.
You get one IP to whitelist. That's it.
Step 1: Create Your Account
Head to pushftp.com/signup and create an account. The free plan gives you 1 connection and 50 transfers per month — enough to set everything up and test your workflows.
No credit card required. You'll land on the dashboard after signup.
Step 2: Grab Your API Key
Go to Settings → API Keys and generate a key. This key authenticates all API requests and Zapier connections.
Keep it safe — treat it like a password. You can generate multiple keys if you want to separate access between different tools or environments.
Authorization: Bearer pftp_live_abc123...
You'll use this key when connecting Zapier, calling the REST API, or setting up webhooks. See the API documentation for all available endpoints.
Step 3: Add Your First Connection
Connections are your file servers. Go to Connections → New Connection and fill in the details.
For SFTP:
Type: SFTP
Host: sftp.example.com
Port: 22
Username: deploy
Auth: Password
Password: ••••••••
For FTP:
Type: FTP
Host: ftp.example.com
Port: 21
Username: uploads
Auth: Password
Password: ••••••••
For S3:
Type: S3
Bucket: my-bucket
Region: eu-west-1
Access Key: AKIA...
Secret Key: ••••••••
Click Test Connection to verify. If it fails, make sure you've added PushFTP's static IP to your server's firewall allow list. The IP is displayed on your dashboard.
Step 4: Connect Zapier
In Zapier, search for PushFTP and add it to a Zap. When prompted, paste your API key. Zapier will validate the connection.
Now you can use any PushFTP action in your Zaps:
- Upload File — send files to your server
- Download File — pull files from your server
- List Files — see what's in a directory
- Read File — get file contents (CSV, JSON, text)
- Delete File — remove files after processing
- Move/Rename File — reorganize remotely
- Copy File — duplicate files across paths
- Create Folder — make directories
- Run SSH Command — execute remote scripts
- Find File — search before acting
And two triggers:
- New File Detected — fires when a watched folder gets a new file
- Transfer Failed — fires when something goes wrong
Read more in the Zapier integration guide.
Step 5: Set Up Watched Folders (Optional)
If you want Zapier to react when files land on your server, set up a watched folder. Go to Connections → (your connection) → Watched Folders and add a path:
Path: /incoming/invoices
Poll interval: 5 minutes
PushFTP polls the folder at the set interval. When a new file appears, it fires the New File Detected trigger in Zapier. From there, you can download it, process it, move it — whatever your workflow needs.
Step 6: Use Filename Templates
When uploading, you can use dynamic filename templates instead of hardcoding names:
/reports/{date}-{original}
/uploads/{uuid}.{ext}
/archive/{datetime}/{name}.{ext}
Available placeholders:
| Template | Example Output |
|---|---|
{date} |
2025-01-15 |
{time} |
14-30-45 |
{datetime} |
2025-01-15T14-30-45 |
{timestamp} |
1705312245 |
{uuid} |
a1b2c3d4-... |
{original} |
report.pdf |
{name} |
report |
{ext} |
pdf |
{counter} |
001 |
This prevents filename collisions and keeps your remote directories organized.
Step 7: Test Your First Transfer
Build a simple Zap to verify everything works:
- Trigger: Schedule by Zapier → Every Day
- Action: PushFTP → Upload File
- Connection: Your SFTP/FTP/S3 connection
- File URL: Any public file URL
- Remote Path:
/test/{date}-test.txt
Run it once. Check your server — the file should appear. If it does, you're good. Delete the test Zap or keep it as a health check.
Understanding Plans
| Plan | Connections | Transfers/mo | Log Retention | Price |
|---|---|---|---|---|
| Free | 1 | 50 | 7 days | €0 |
| Starter | 1 | Unlimited | 7 days | €9/mo |
| Pro | 5 | Unlimited | 30 days | €29/mo |
| Business | 10 | Unlimited | 90 days | €59/mo |
Start free. Upgrade when you need more connections or hit the transfer limit. No feature gates between plans except connection count and log retention.
Other Ways to Use PushFTP
Beyond Zapier, you can use PushFTP's REST API directly. It uses Bearer token authentication with your API key:
curl -X POST https://api.pushftp.com/v1/upload \
-H "Authorization: Bearer pftp_live_abc123" \
-F "connection=conn_xyz" \
-F "path=/uploads/report.pdf" \
-F "[email protected]"
You can also use email upload addresses — PushFTP gives you a unique email address that forwards attachments to your configured connection. Handy for forwarding invoices or reports from systems that only support email output.
Webhooks work in the other direction: PushFTP can POST to a URL when a file event happens, so you can trigger workflows in Make, n8n, or your own backend.
PushFTP takes about two minutes to set up — create an account, add a connection, grab your API key, and you're transferring files. The free plan covers 50 transfers a month, enough to build and test your entire workflow before upgrading.
FAQ
How is PushFTP different from EasyFTP?
Both solve the Zapier-to-SFTP problem. PushFTP starts free (EasyFTP starts at $39/month), supports S3 connections, and offers features like email uploads, webhooks, and SSH command execution. PushFTP also provides a REST API for non-Zapier integrations.
Do I need a static IP on my end?
No. PushFTP provides the fixed IP. Your automation tools (Zapier, Make, etc.) connect to PushFTP's API over HTTPS. PushFTP then connects to your server from its static IP. You only need to whitelist PushFTP's IP on your file server.
Can I use PushFTP with Make or n8n?
Yes. Use the REST API with your API key. Any tool that can make HTTP requests works. The API documentation covers all endpoints.
Start Building
You've got the account, the API key, the connection, and the Zapier integration. The rest is about combining these pieces into workflows that match what you actually need. Pick an action, wire it up, and test it. PushFTP handles the plumbing so you can focus on the automation logic.