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 is designed to delete specific metadata entries associated with an order in a system, identified by the order's unique ID. It targets metadata keys such as imei, uin, gtin, or sgtin and removes the corresponding metadata for the given order. This operation is useful in scenarios where metadata needs to be cleaned up or corrected after order processing, for example, removing outdated or incorrect identifiers linked to an order.
Practical examples include:
- Removing an incorrect IMEI number from an order's metadata.
- Deleting a GTIN code that was mistakenly assigned to an order.
- Clearing any single metadata key related to an order when it is no longer valid.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly order whose metadata is to be deleted (number). |
| Key | The name of the metadata key to delete. Only one key can be specified at a time. Possible values: imei, uin, gtin, sgtin. |
Output
The node outputs JSON data representing the result of the deletion request. Typically, this will confirm whether the metadata key was successfully deleted for the specified order. The exact structure depends on the API response but generally includes status information about the deletion operation.
No binary data output is expected from this node.
Dependencies
- Requires access to an external API endpoint related to order metadata management.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL and request headers are set according to the bundled OpenAPI specification, which must be accessible.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Order Id may result in errors or no action.
- Specifying a metadata key not supported (
imei,uin,gtin,sgtin) will likely cause the API to reject the request. - Missing or incorrect API authentication credentials will prevent successful communication with the service.
Error messages:
- "Order not found" — Verify the Order Id is correct and exists.
- "Invalid metadata key" — Ensure the key is one of the allowed values.
- "Unauthorized" or "Authentication failed" — Check API credentials configuration in n8n.
Links and References
- No direct external links provided in the source code.
- Refer to the API documentation of the order metadata service for detailed information on metadata keys and deletion behavior.