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 update metadata related to orders. In particular, the "Put Orders Meta Uin By Orderid" operation allows users to associate or update a unique identifier (UIN) for a given order by specifying the order's ID. This is useful in scenarios where you need to track or link additional metadata to an order, such as payment identifiers, tracking numbers, or other unique codes.
Practical examples include:
- Updating an order record with a payment transaction ID.
- Associating a government-issued unique identification number with an order for compliance or auditing.
- Linking external system references to internal order records.
Properties
| Name | Meaning |
|---|---|
| Order Id | The numeric identifier of the assembly or order task that you want to update metadata for. |
| Uin | The unique identification number (UIN) string to associate with the specified order. |
Output
The node outputs JSON data representing the response from the API after attempting to update the order metadata. This typically includes confirmation of the update or details about the updated resource. The exact structure depends on the API but generally contains status information and possibly the updated order metadata.
No binary data output is indicated.
Dependencies
- Requires access to an external API endpoint defined by the base URL extracted from the bundled swagger JSON.
- Needs an API key or authentication token configured in n8n credentials to authorize requests to the API.
- Uses HTTP headers specifying JSON content type and acceptance.
- Relies on the
@devlikeapro/n8n-openapi-nodepackage for building request properties and handling OpenAPI specifications.
Troubleshooting
- Common issues:
- Invalid or missing Order Id or UIN values will cause the API to reject the request.
- Authentication failures if the API key or token is not set or expired.
- Network connectivity problems preventing communication with the API server.
- Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials configuration.
- "Order not found": Verify the Order Id exists and is correct.
- "Invalid UIN format": Ensure the UIN string matches expected formatting rules.
- To resolve errors, verify input parameters, ensure valid credentials, and confirm network access to the API endpoint.
Links and References
- No direct external links provided in the source code.
- Refer to the API documentation corresponding to the used swagger JSON (
03-orders-fbs_modified.json) for detailed API behavior and schema. - Consult n8n documentation on setting up API credentials and using custom nodes.