Generate X12 004010 EDI 850 PO Files in n8n Workflow

Generate compliant X12 004010 EDI 850 Purchase Order files directly from your JSON in n8n

This n8n sub-workflow converts a canonical purchase order JSON into an ANSI X12 004010 EDI 850 text payload, then packages it as a downloadable .edi file—ready for storage or delivery to your trading partner.

What this workflow does

• Receives a purchase order object when triggered by another n8n workflow (sub-workflow style).
• Builds a full X12 004010 EDI 850 message using the PO header and line items, mapping units of measure to X12 UOM codes and calculating control totals.
• Creates the required EDI envelopes, including ISA/GS/ST through SE/GE/IEA, based on the provided header and line data.
• Generates a filename from the PO number and converts the generated EDI text into a .edi file output for downstream use.

Use cases

• Send EDI 850 purchase orders from an internal SaaS app by first normalizing order data into the expected JSON structure.
• Automate partner onboarding by adjusting trading-partner identifiers and qualifiers (sender/receiver IDs and usage indicator) in the EDI generation code.
• Store EDI outputs in a document system or deliver them via your existing integrations by consuming the produced .edi file.

Technical details

• Nodes/tech stack: code, sticky note, convert to file, execute workflow trigger.
• Key configuration: set SENDER_ID, RECEIVER_ID, SENDER_QUAL, RECEIVER_QUAL, and the test/production usage indicator in the EDI generation code.
• Expected input shape: a header plus a lines array containing quantity, unit_price, uom, with optional item_code and description.
• Standards-aware formatting: update default currency or date formats in the code to match your trading partner’s requirements.