Overview
The "Orderful Transaction" node enables managing Electronic Data Interchange (EDI) transactions through the Orderful platform. It supports creating, listing, retrieving, confirming delivery, and acknowledging EDI transactions such as purchase orders, invoices, and shipment notices.
This node is beneficial in automating supply chain communications, integrating EDI workflows into automation pipelines, and ensuring seamless data exchange with trading partners. For example, a user can create a new purchase order transaction (850) by providing the transaction data and partner ID, or confirm delivery of multiple transactions to update their status in Orderful.
Properties
| Name | Meaning |
|---|---|
| Transaction Type | The type of EDI transaction to create. Options: Purchase Order (850), Purchase Order Acknowledgment (855), Ship Notice/Manifest (856), Invoice (810), Motor Carrier Load Tender (204), Response to Load Tender (990), Transportation Carrier Shipment Status (214) |
| Transaction Data | The transaction data in JSON format representing the content of the EDI transaction. |
| Partner ID | The identifier of the trading partner for whom the transaction is created. |
Output
The node outputs JSON data representing the response from the Orderful API for the requested operation. For the "Create" operation, this typically includes details about the newly created transaction such as its ID, type, status, and metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Orderful API.
- Needs configuration of the base URL and API key in the node credentials.
- Uses HTTP requests to interact with the Orderful REST API endpoints.
Troubleshooting
- Invalid JSON in transaction data: If the "Transaction Data" input is not valid JSON, the node will throw an error. Ensure that the JSON string is correctly formatted.
- Authentication errors: If the API key or base URL is incorrect or missing, requests will fail. Verify the credential setup.
- Missing required fields: The "Partner ID" and "Transaction Data" are mandatory for creating transactions; omitting them will cause errors.
- API rate limits or network issues: These may cause request failures; check connectivity and API usage limits.
Links and References
- Orderful API Documentation (for detailed API endpoint information)
- EDI Transaction Types (for understanding standard EDI codes like 850, 810, etc.)