FTP and MySQL: Vendor Payment File Import Template
A scheduled Spojit workflow picks up the vendor payment-confirmation file from FTP, parses the CSV, and writes each cleared payment into a MySQL table so AP records stay current.
What It Builds
A Schedule trigger fires on your chosen cadence and a ftp Connector node downloads the latest payment-confirmation file. A csv utility node parses the rows, a Loop node walks each cleared payment, and a mysql Connector node in Direct mode inserts each record into your payments table. The result: AP records reconcile themselves without anyone re-keying a bank file.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every weekday at 7am, downloads the latest vendor payment-confirmation CSV from our FTP server, parses each row, and inserts one record per cleared payment into the MySQL payments table with the vendor name, invoice number, amount, and cleared date.Connectors Used
- Schedule trigger - runs the import on a fixed cron cadence in your timezone.
- ftp - retrieves the vendor payment-confirmation file from the remote server.
- csv - parses the downloaded file into structured rows.
- mysql - inserts each cleared payment into your AP table.
Customize It
Adjust the schedule time, the FTP path or filename pattern, and the target table name directly in the prompt. You can also change which columns map into MySQL (for example add a currency or batch_id field), or have it skip rows where the status is not cleared.
Tips
- Give the FTP connection an account scoped to the payments folder only, so the run cannot touch other directories.
- Keep the MySQL node in Direct mode for a clean, low-cost insert; no AI is needed for a straight import.
- If files occasionally arrive late, widen the schedule or add a check that the expected filename exists before parsing.