Overview
This node interacts with the Orderful platform to manage EDI (Electronic Data Interchange) transactions. It supports operations such as listing transactions, creating new transactions, retrieving specific transactions or their messages, confirming delivery of transactions, and creating acknowledgments.
A common use case is automating the retrieval and management of EDI transaction data between trading partners, which helps streamline supply chain communications and order processing workflows. For example, a user can list recent purchase orders filtered by status and date, create new shipment notices, or confirm that certain transactions have been delivered.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Collection of optional filters for listing transactions: |
| - End Date: Filter transactions created before this date | |
| - Limit: Maximum number of results to return (minimum 1, default 50) | |
| - Start Date: Filter transactions created after this date | |
| - Status: Filter by transaction status; options are Pending, Processed, Failed, Delivered | |
| - Transaction Type: Filter by transaction type (e.g., "850", "810") |
Output
The node outputs JSON data representing the result of the selected operation:
- For List operation: an array of transaction objects matching the filter criteria.
- For Create operation: details of the newly created transaction.
- For Get operation: details of the specified transaction.
- For Get Message operation: the message content of the specified transaction.
- For Confirm Delivery operation: confirmation response indicating successful delivery acknowledgment.
- For Create Acknowledgment operation: details of the created acknowledgment.
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 to communicate with the Orderful service.
Troubleshooting
- Invalid JSON in transaction data: When creating a transaction, the
transactionDataproperty must contain valid JSON. Invalid JSON will cause an error. Ensure the JSON syntax is correct before running. - API authentication errors: If the API key or base URL is incorrect or missing, requests will fail. Verify credentials configuration.
- Filtering issues: When using filters in the List operation, ensure date formats and status values are valid according to the API expectations.
- Empty or missing required fields: Some operations require mandatory fields like
transactionIdorpartnerId. Omitting these will cause errors. - Handling multiple transaction IDs: For confirming delivery, provide a comma-separated list of transaction IDs without extra spaces.
Links and References
- Orderful API Documentation (for detailed API endpoints and data formats)
- EDI Standards Overview (background on common transaction types like 850, 810)