FTP CSV to JSON File Transform Template
A scheduled workflow that downloads a CSV file from FTP, converts it to a JSON array, and uploads the result back to FTP for API-ready consumption.
What It Builds
A Schedule trigger runs on a cron you set and fires a Connector node on the ftp connector to download a CSV file. A second Connector node on the csv connector converts the rows to a JSON array, and a final ftp node uploads the JSON file to an output folder. The result is a clean, structured JSON file that downstream systems can pick up without re-parsing CSV.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every morning at 6am Australia/Sydney time, downloads the file /exports/orders.csv from my FTP connection, converts the CSV rows into a JSON array with the csv connector, and uploads the result as /exports/orders.json back to the same FTP connection.
Connectors Used
- Schedule trigger - runs the workflow on a 5-field cron and IANA timezone.
- ftp -
download-filepulls the source CSV andupload-filewrites the JSON back. - csv -
to-jsonturns the parsed rows into a JSON array.
Customize It
Change the cron and timezone in the prompt for a different run time, swap the source and destination file paths to match your folders, or point the upload at a separate output directory. To reshape rows before output, ask Miraxa to add a Transform node between the convert and upload steps.
Tips
- Make sure your FTP connection has write access to the upload folder, not just read.
- Keep both ftp nodes in Direct mode: the paths are predictable, so no AI credits are needed.
- For large files, watch FTP transfer limits and split exports into smaller batches if needed.
Related
- Want the step-by-step? See How to Transform CSV Data to JSON for API Uploads.
- How to Export Orders to CSV via FTP.