Actions16
- Сборочные Задания DBS Actions
- Метаданные DBS Actions
Overview
This node interacts with a specific API to update metadata related to DBS (likely "Dropship by Seller") orders. The particular operation "Put Dbs Orders Meta Sgtin By Orderid" allows users to associate or update an array of marking codes (Sgtins) for a given assembly order identified by its Order Id.
Common scenarios where this node is useful include:
- Updating product tracking or serialization information for an existing DBS order.
- Managing and synchronizing marking codes for orders in supply chain or logistics workflows.
- Automating the enrichment of order metadata with serialized product identifiers.
For example, if you have an order with ID 5632423 and want to attach a list of serialized GTINs (Sgtins) to it, this node lets you send that data directly to the backend system managing DBS orders.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly order to update. Required numeric value. |
| Sgtins | A JSON array of marking codes (serialized GTINs). Each code must be between 16 and 135 characters. |
Output
The node outputs JSON data representing the response from the API after updating the order metadata. This typically includes confirmation of the update or details about the updated order metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the WB API (or equivalent).
- Depends on the base URL and schema defined in the bundled OpenAPI specification (
04-orders-dbs_modified.json). - Uses HTTP headers
Accept: application/jsonandContent-Type: application/json. - No additional external services beyond the configured API endpoint are required.
Troubleshooting
- Invalid Order Id: If the provided Order Id does not exist or is incorrect, the API may return an error indicating the order was not found. Verify the Order Id before running the node.
- Malformed Sgtins JSON: The Sgtins property expects a valid JSON array of strings. Invalid JSON or codes outside the allowed length range (16 to 135 characters) may cause errors.
- Authentication Errors: Missing or invalid API credentials will result in authorization failures. Ensure the API key or token is correctly configured.
- Network Issues: Connectivity problems to the API endpoint can cause timeouts or connection errors. Check network access and endpoint availability.
Links and References
- WB API Documentation (example link, replace with actual if available)
- Serialization and Marking Codes Standards (for understanding Sgtins format)
If you need further details on other operations or resources, please provide their names.