Repository navigation
FTP Connection Flow Actions Save file from URL
Devices / FTP Connection / Flowcards / Actions
Copy a file from an HTTP, HTTPS, or FTP address to your FTP Connection. Homey downloads the source and uploads its bytes to the destination. This avoids putting the complete file into a base64 Flow token.
| Field | What to enter |
|---|---|
| FTP Connection | Your destination server device. |
| URL | A direct file address reachable from Homey, not a page containing a download button. |
| Path | Optional destination directory selected from the picker. |
| Filename | The destination filename, optionally including a relative path. Supports BLL coding. |
With no Path selected, the filename is relative to the device's configured working directory. With a Path selected, it is relative to that directory. The source URL is literal text or a Flow token; this card does not evaluate BLL expressions in the URL field.
There are no output tokens. Connect the successful completion to the next step, and the error output to a short notification or log message.
Before saving: an existing destination file with the same name is overwritten. Start in a writable test directory with an unused filename.
- Choose a small text file on a server you control. Check that Homey can reach its direct URL without an interactive sign-in.
- Add Save file from URL to a manually started Advanced Flow.
- Select your FTP Connection, choose a test Path, and enter
download-test.txt. - Put the direct file URL in URL. Save the Flow before running it.
- After success, open Repair,
refresh that directory, and download
download-test.txt.

Actual Homey card examples, saved but disabled. They have not been run; follow this page for the full setup and connections.
The downloaded copy should contain the same text as the source. Renaming the extension does not convert the file.
- HTTP and HTTPS sources must return status
200. The app follows up to five HTTP redirects. HTTPS certificates are verified. - The source connection and inactive HTTP response have a 30-second timeout; this is not a promise that an entire large transfer finishes in 30 seconds.
- FTP source URLs must point to a file. They use plain FTP, not FTPS or SFTP. Avoid putting source credentials in a shared Flow or screenshot.
- The destination's own connection/security settings are independent of the source protocol. Normal destination retry and transfer-error behavior still applies; check the error branch and the saved file after a failure.
- A temporary link can expire before a later retry. Generate it just before saving. For Simple (Sys) Log use the dedicated Save a Simple (Sys) Log export card, which waits for a complete export.
Support development - If FTP Client is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!