Overview
This node integrates with the Orderful EDI platform to convert data between different EDI and JSON formats. It is particularly useful when working with electronic data interchange (EDI) documents that need to be transformed from one standard format to another, such as converting X12 or EDIFACT messages into JSON for easier processing, or vice versa.
Common scenarios include:
- Transforming incoming EDI messages (X12 or EDIFACT) into JSON for internal processing or storage.
- Converting JSON representations of EDI data back into X12 or EDIFACT formats for transmission to trading partners.
- Automating EDI workflows by integrating format conversion directly within n8n workflows.
Example: A user receives an X12 purchase order message and wants to convert it into JSON to extract specific fields and update their database. Later, they might convert updated JSON data back into EDIFACT format to send to a partner.
Properties
| Name | Meaning |
|---|---|
| From Format | The format of the input data. Options: X12, JSON, EDIFACT. |
| To Format | The desired output format after conversion. Options: JSON, X12, EDIFACT. |
| Data | The actual data string to convert. This should be a valid string in the specified "From Format". |
Output
The node outputs a JSON object representing the converted data. The structure depends on the target format:
- If converting to JSON, the output will be a parsed JSON representation of the original EDI data.
- If converting to X12 or EDIFACT, the output will be a string formatted according to the respective EDI standard.
The output is provided in the json field of the node's output items.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Orderful EDI platform via an API key credential.
- The node uses the Orderful API endpoint
/conversionto perform the data transformation. - Proper configuration of the API base URL and authentication token is necessary in the node credentials.
Troubleshooting
- Invalid data format errors: Ensure that the input data matches the declared "From Format". For example, if "From Format" is set to
x12, the data must be a valid X12 message. - Conversion failures: These may occur if the data contains syntax errors or unsupported segments. Validate the source data before conversion.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Empty output: Check that the input data is not empty and that the "To Format" is different from the "From Format" to avoid no-op conversions.