Actions34
- Сборочные Задания Actions
- Метаданные Actions
- Поставки FBS Actions
- Post Supplies
- Get Supplies
- Patch Supplies Orders By Supplyid By Orderid
- Get Supplies By Supplyid
- Delete Supplies By Supplyid
- Get Supplies Orders By Supplyid
- Patch Supplies Deliver By Supplyid
- Get Supplies Barcode By Supplyid
- Get Supplies Trbx By Supplyid
- Post Supplies Trbx By Supplyid
- Delete Supplies Trbx By Supplyid
- Patch Supplies Trbx By Supplyid By Trbxid
- Delete Supplies Trbx Orders By Supplyid By Trbxid By Orderid
- Post Supplies Trbx Stickers By Supplyid
- Пропуска Actions
- Доставка Курьером WB DBW Actions
Overview
This node interacts with a specific API to retrieve metadata about orders based on a given order ID. It is designed to fetch detailed information related to an assembly or fulfillment task identified by the order ID. This functionality is useful in scenarios where users need to programmatically access order metadata for tracking, reporting, or integration purposes.
For example, a user might use this node to:
- Retrieve status and details of a particular order in a warehouse management system.
- Automate workflows that depend on order metadata, such as triggering notifications or updating databases.
- Integrate order data into dashboards or analytics tools.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly or fulfillment order to retrieve metadata for. |
Output
The node outputs JSON data containing the metadata of the specified order. The structure of the JSON output corresponds to the API response schema for order metadata, which typically includes fields such as order status, timestamps, item details, and other relevant attributes describing the order.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate requests to the external API.
- Depends on a base URL configured from an imported OpenAPI specification.
- Uses HTTP headers specifying JSON content type for communication.
- The node relies on an external OpenAPI client library to build and send requests.
Troubleshooting
- Common issues:
- Invalid or missing order ID may result in errors or empty responses.
- Authentication failures if the API key credential is not set or invalid.
- Network connectivity problems can cause request timeouts or failures.
- Error messages:
- "Unauthorized" or similar indicates authentication issues; verify API credentials.
- "Not Found" or equivalent suggests the order ID does not exist; check the input value.
- JSON parsing errors may occur if the API response format changes unexpectedly.
Links and References
- Refer to the external API documentation for detailed descriptions of order metadata fields and usage guidelines.
- Consult the OpenAPI specification used by the node for the full schema of supported operations and properties.