Overview
The "Orderful Transaction" node manages EDI (Electronic Data Interchange) transactions within the Orderful platform. It supports operations such as creating new transactions, retrieving transaction details or messages, listing transactions with filters, confirming delivery of transactions, and creating acknowledgments.
This node is beneficial in automating supply chain communications, order processing, invoicing, and shipment tracking by integrating EDI workflows directly into n8n automation pipelines. For example, a user can automatically fetch the latest purchase orders, confirm their delivery status, or generate acknowledgments without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Transaction ID | The unique identifier of the transaction to retrieve or operate on. |
Note: This property is required for the "Get" and "Get Message" operations.
Output
The node outputs JSON data representing the response from the Orderful API for the selected operation. The structure varies depending on the operation:
- For Get Message, the output contains the message content of the specified transaction.
- For Get, it returns detailed information about the specific transaction.
- For other operations like Create, List, Confirm Delivery, and Create Acknowledgment, the output reflects the respective API responses, typically including transaction metadata or confirmation statuses.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Orderful API.
- The base URL for the Orderful API must be configured in the credentials.
- Uses HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Invalid JSON in transaction data: When creating a transaction, the "Transaction Data" input must be valid JSON. Invalid JSON will cause an error. Ensure the JSON syntax is correct before running the node.
- Missing required fields: Operations like "Get Message" require a valid "Transaction ID". Omitting this will result in errors.
- API authentication errors: If the API key or base URL is incorrect or missing, requests will fail. Verify credential configuration.
- Rate limits or network issues: API calls may fail due to rate limiting or connectivity problems. Implement retry logic or check network status if errors occur.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Orderful API Documentation (for detailed API endpoints and data formats)
- n8n Documentation - Creating Custom Nodes