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
This node integrates with the Bitrix24 platform, specifically allowing users to add a new property to a product in the Bitrix24 CRM system. It is useful for extending the product data model by defining custom attributes or metadata that better fit specific business needs.
Typical use cases include:
- Adding custom fields to products to capture additional information such as warranty period, manufacturer details, or special categorizations.
- Automating product catalog updates by programmatically adding properties during import or synchronization workflows.
- Enhancing reporting and filtering capabilities by introducing new product attributes.
For example, a user might add a "Color" property of type "List" with predefined values like "Red, Blue, Green" to classify products by color.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Property Name | The display name of the product property to add. |
| Property Code | The unique code identifier for the product property. |
| Property Type | The data type of the property. Options: String, Number, List, File, Date, DateTime, HTML, Element, GPS, User. |
| Property Required | Whether this property must have a value (true/false). |
| Property Sort Order | Numeric value determining the order in which the property appears relative to others. |
| Property Multiple | Whether the property can hold multiple values (true/false). |
| Property Active | Whether the property is active/enabled (true/false). |
| Property Values | For list-type properties, a collection containing a comma-separated list of allowed values. |
Output
The node outputs an array of items where each item contains a json object representing the result of the add property operation. This typically includes confirmation details from Bitrix24 about the newly created property.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is produced by this node.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions to modify product properties.
- Supports three authentication methods: OAuth2, webhook URL, or API key. Proper credentials must be configured in n8n accordingly.
- Relies on Bitrix24's REST API endpoints for CRM product management.
Troubleshooting
Common issues:
- Invalid or missing authentication credentials will cause authorization failures.
- Providing duplicate or invalid property codes may result in API errors.
- Incorrect property types or malformed property values (especially for list types) can cause request rejections.
Error messages:
- Errors returned from Bitrix24 API are surfaced in the node output under the
errorfield if "Continue On Fail" is enabled. - Typical error messages include authentication failures, validation errors for property parameters, or network connectivity issues.
- Errors returned from Bitrix24 API are surfaced in the node output under the
Resolutions:
- Verify that the selected authentication method is correctly set up and credentials are valid.
- Ensure property codes are unique and conform to Bitrix24 naming rules.
- Validate that list-type property values are properly formatted as comma-separated strings.
- Check network connectivity and Bitrix24 service status if requests fail unexpectedly.