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 updates information about a specific pass (пропуск) identified by its Pass Id. It is designed to modify details such as the driver's first and last name, car model, car number, and associated office ID for an existing pass record. This operation is useful in scenarios where pass details need correction or updating after initial creation, for example, when a driver changes their vehicle or personal information needs to be corrected.
Practical examples:
- Updating the car model and number after a driver switches vehicles.
- Correcting the driver's name spelling on an existing pass.
- Changing the office location associated with the pass.
Properties
| Name | Meaning |
|---|---|
| Pass Id | The unique identifier of the pass to update. |
| First Name | Driver's first name. |
| Last Name | Driver's last name. |
| Car Model | The make or brand of the car. |
| Car Number | The license plate number of the car. |
| Office Id | Identifier of the warehouse or office related to the pass. |
Output
The node outputs JSON data representing the updated pass information after the PUT request completes successfully. The output typically includes the updated fields reflecting the new values sent in the request. There is no indication that binary data is returned by this node.
Dependencies
- Requires an API key credential or similar authentication token to interact with the external service managing passes.
- The node uses a base URL configured from an imported OpenAPI specification.
- The node sends HTTP PUT requests with JSON bodies containing the updated pass data.
Troubleshooting
Common issues:
- Invalid or missing Pass Id will cause the update to fail.
- Incorrect or incomplete required fields (e.g., missing first or last name) may result in validation errors.
- Authentication failures if the API key or token is not set or expired.
- Network or connectivity issues preventing communication with the external API.
Error messages and resolutions:
- "Pass not found" — Verify that the Pass Id exists and is correct.
- "Validation error" — Ensure all required fields are provided and correctly formatted.
- "Unauthorized" — Check that the API credentials are properly configured and valid.
- "Network error" — Confirm network connectivity and API endpoint availability.
Links and References
- No direct links available from the source code. For more information, consult the API documentation of the external service managing passes.