Actions16
- Сборочные Задания DBS Actions
- Метаданные DBS Actions
Overview
This node interacts with a specific API related to "Метаданные DBS" (DBS Metadata) and provides an operation to delete metadata entries associated with DBS orders by their order ID. The primary use case is to remove certain metadata fields such as imei, uin, gtin, or sgtin from a given assembly order identified by its unique order ID.
Practical examples include:
- Cleaning up or correcting metadata for an order when incorrect or outdated identifiers were attached.
- Managing inventory or product tracking data by removing obsolete metadata keys linked to orders.
- Automating the maintenance of order metadata in workflows that integrate with the DBS system.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly order whose metadata you want to delete (required). |
| Key | The name of the metadata key to delete. Only one value can be provided. Options include: imei, uin, gtin, sgtin. |
Output
The node outputs JSON data representing the result of the deletion request. This typically includes confirmation of the deletion or any error messages returned by the API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential to authenticate requests to the WB API.
- Depends on the base URL and OpenAPI specification defined in the bundled swagger JSON file.
- Uses HTTP headers specifying JSON content type and acceptance.
- No additional external services beyond the WB API are indicated.
Troubleshooting
Common issues:
- Providing an invalid or non-existent order ID may result in errors or no action.
- Specifying a metadata key not supported (other than imei, uin, gtin, sgtin) will likely cause the API to reject the request.
- Missing or invalid API authentication credentials will prevent successful execution.
Error messages:
- Errors related to authorization usually indicate missing or incorrect API keys.
- Validation errors may occur if required parameters like Order Id or Key are missing or malformed.
- Network or connectivity errors should be checked by verifying endpoint accessibility and internet connection.
Links and References
- WB API Documentation (replace with actual link if available)
- n8n documentation on creating custom nodes