Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, for the Product resource and the Update Product operation, this node updates an existing product's details in a Bitrix24 catalog.
This is useful when you want to automate product management workflows such as updating prices, descriptions, stock quantities, or other product attributes directly from your automation workflows without manual intervention.
Practical examples:
- Automatically update product prices based on supplier data.
- Change product availability status after inventory sync.
- Modify product descriptions or categories based on marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key |
| Product ID | The unique identifier of the product to update |
| Product Name | The name/title of the product |
| Price | The price of the product |
| Currency | Currency code for the price (e.g., RUB, USD, EUR) |
| Catalog ID | Identifier of the catalog where the product belongs |
| Section ID | Identifier of the product section or category |
| Active | Boolean indicating if the product is active |
| Sort Order | Numeric value defining the sort order of the product |
| Description | Text description of the product |
| Code | Product code or SKU |
| XML ID | External identifier used for integration |
| Weight | Weight of the product |
| Width | Width dimension of the product |
| Length | Length dimension of the product |
| Height | Height dimension of the product |
| Measure | Unit of measure for the product |
| VAT ID | Identifier for the VAT rate |
| VAT Included | Boolean indicating whether VAT is included in the price |
| Quantity | Available quantity of the product |
| Quantity Trace | Mode of quantity tracking; options are "D", "Y", or "N" |
| Can Buy Zero | Boolean indicating if purchase is allowed when quantity is zero |
| Subscribe | Boolean indicating if subscription is allowed when out-of-stock |
Output
The node outputs an array of items, each containing a json object representing the response from Bitrix24 after attempting to update the product. This typically includes confirmation of the updated product fields or error information if the update failed.
If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use)
- Bitrix24 webhook URL (simpler but less secure)
- API key authentication
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to Bitrix24 API endpoints is required.
Troubleshooting
Common issues:
- Invalid or missing Product ID will cause the update to fail.
- Incorrect authentication credentials or expired tokens will result in authorization errors.
- Providing invalid field values (e.g., negative price, unsupported currency code) may cause API validation errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned by Bitrix24 API will be surfaced in the node output under the
errorfield if "Continue On Fail" is enabled. - Common error messages include authentication failures, missing required fields, or invalid parameter formats.
- Errors returned by Bitrix24 API will be surfaced in the node output under the
Resolution tips:
- Verify that the Product ID exists in Bitrix24 before attempting an update.
- Ensure credentials are valid and have sufficient permissions.
- Double-check all input property values for correctness and completeness.
- Enable "Continue On Fail" to capture errors gracefully and debug issues.