Overview
This node retrieves detailed information about a specific order from the Jelp Delivery service. It is useful when you need to fetch the current status, contents, or metadata of an order identified by its folio or public ID. Typical use cases include tracking orders, integrating order details into workflows, or synchronizing order data with other systems.
Properties
| Name | Meaning |
|---|---|
| Order | Folio or publicId of the order |
Output
The node outputs an array of JSON objects, each representing the detailed data of the requested order as returned by the Jelp Delivery API. The structure corresponds directly to the API response for an order and includes all available fields such as order status, items, customer info, timestamps, etc.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Jelp Delivery API.
- The node makes HTTP GET requests to the endpoint
/dev/v1/order/{reference}on the Jelp Delivery base URL. - Proper configuration of the API credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing order reference will cause the API to return an error or empty result.
- Authentication failures if the API key credential is not set up correctly.
- Network or connectivity problems may prevent reaching the Jelp Delivery API.
Error messages:
- Errors related to authentication typically indicate misconfigured or expired API credentials.
- Parsing errors might occur if the API returns unexpected data; ensure the API version and endpoint are correct.
Resolutions:
- Verify the order reference value is correct and exists in the Jelp Delivery system.
- Check that the API key credential is valid and has the required permissions.
- Confirm network access to the Jelp Delivery API endpoint.
Links and References
- Jelp Delivery API Documentation (hypothetical link for reference)
- n8n documentation on HTTP Request Node for understanding request handling and authentication setup