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 post vehicle pass information ("Пропуска") to a remote service, likely related to warehouse or office access management. It collects driver and vehicle details such as the driver's first and last name, car model, car number, and the office ID where the pass is valid. This node would be beneficial in scenarios where automated registration of vehicle passes is required, for example, in logistics companies managing vehicle access to warehouses or restricted areas.
Practical examples include:
- Automatically issuing vehicle passes when a delivery is scheduled.
- Integrating with an internal system to register visitor vehicles.
- Managing fleet access permissions dynamically based on incoming data.
Properties
| Name | Meaning |
|---|---|
| First Name | Driver's first name (e.g., "Александр") |
| Last Name | Driver's last name (e.g., "Петров") |
| Car Model | Vehicle brand or model (e.g., "Lamborghini") |
| Car Number | Vehicle license plate number (e.g., "A456BC123") |
| Office Id | Numeric identifier of the office or warehouse where the pass applies |
Output
The node outputs JSON data representing the response from the remote API after posting the pass information. The exact structure depends on the external service but typically includes confirmation details about the created pass, such as IDs, status, or error messages if any.
There is no indication that this node outputs binary data.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests to the external service.
- Depends on a base URL defined in the node’s configuration, which points to the API endpoint handling pass registrations.
- Uses HTTP POST requests with JSON payloads containing the input properties.
Troubleshooting
Common issues:
- Missing or invalid API credentials can cause authorization failures.
- Incorrect office ID or malformed vehicle data may result in validation errors from the API.
- Network connectivity problems could prevent successful requests.
Error messages:
- Authorization errors typically indicate missing or incorrect API keys; verify credential setup.
- Validation errors from the API usually specify which input field is problematic; check property values.
- Timeout or connection errors suggest network issues; ensure the API endpoint is reachable.
Links and References
- No direct links are provided in the source code.
- For further details, consult the documentation of the external API managing vehicle passes or the n8n community forums for similar node usage examples.