Actions16
- Сборочные Задания DBS Actions
- Метаданные DBS Actions
Overview
This node is designed to interact with a specific API related to "Сборочные Задания DBS" (Assembly Tasks DBS). The particular operation "Post Dbs Orders Status" allows users to post or update the status of assembly orders by sending a list of order identifiers. This can be useful in workflows where you need to programmatically update or synchronize the status of multiple assembly tasks in bulk.
Practical examples include:
- Automatically updating the status of assembly orders after a manufacturing step completes.
- Synchronizing order statuses between different systems or databases.
- Triggering downstream processes based on updated order statuses.
Properties
| Name | Meaning |
|---|---|
| Orders | A JSON array containing the list of assembly order identifiers to update the status for. |
The "Orders" property expects a JSON-formatted list of numeric IDs representing the assembly tasks whose statuses are to be posted or updated.
Output
The node outputs JSON data corresponding to the response from the API after posting the orders' statuses. The exact structure depends on the API's response but typically includes confirmation of the update, any errors per order, or overall status messages.
There is no indication that this node outputs binary data.
Dependencies
- Requires an API key credential for authentication with the WB API (or equivalent).
- Depends on the external WB API endpoint defined in the bundled Swagger/OpenAPI specification (
04-orders-dbs_modified.json). - Uses a base URL configured from the OpenAPI spec.
- Requires network access to the WB API service.
Troubleshooting
- Invalid JSON in Orders: If the "Orders" input is not valid JSON, the node will fail to parse it. Ensure the input is a properly formatted JSON array of numbers.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
- API Endpoint Issues: Network problems or changes in the API endpoint may cause request failures. Check connectivity and confirm the API URL has not changed.
- Empty or Incorrect Order IDs: Sending empty arrays or invalid order IDs might result in errors or no updates. Validate the order IDs before sending.
Links and References
- WB API Documentation (Replace with actual link if available)
- OpenAPI Specification Reference
- n8n Documentation on Creating Custom Nodes