FTP to NetSuite: EDI 850 Purchase Order Intake Template

This Spojit template polls an FTP drop folder for inbound EDI 850 purchase order files, parses each one, and creates the matching NetSuite sales order so fulfillment can start without manual keying.

What It Builds

A Schedule trigger runs on your chosen interval and a Connector node in Direct mode lists and downloads new files from your FTP drop folder. A Loop node walks each EDI 850 file, a Transform node maps the parsed line items and header fields into NetSuite shape, and a NetSuite Connector node creates the sales order. Each order is logged so trading partners flow straight into fulfillment.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every 15 minutes, connects to my FTP server, and downloads any new EDI 850 purchase order files from the /inbound folder. For each file, parse the order header and line items, then create a matching NetSuite sales order with the buyer, ship-to address, requested ship date, and each item SKU and quantity. After a sales order is created successfully, move the source file to a /processed folder.

Connectors Used

Schedule trigger - polls the FTP folder on a fixed cron interval.
FTP - lists, downloads, and moves the inbound EDI 850 files.
NetSuite - creates the sales order for each parsed purchase order.
CSV - parses tabular line-item data when partners send delimited files.

Customize It

Change the poll interval, the /inbound and /processed folder paths, or the trading-partner identifier in the prompt. Add fields such as PO number, payment terms, or location to the NetSuite mapping, and adjust which item identifier (SKU, UPC, or internal id) is used for line matching.

Tips

Your FTP connection needs read and write access so processed files can be moved out of the inbound folder and never reprocessed.
Use a Connector node in Direct mode for the NetSuite create call to keep runs deterministic with no AI cost; switch to Agent mode only if partner formats vary widely.
Map line items to existing NetSuite item records first so unmatched SKUs surface clearly instead of failing the whole order.