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 an entity item within Bitrix24's data storage system. It is useful for extending CRM entities or other business objects by defining custom properties that can hold additional information.
Typical use cases include:
- Adding custom fields to CRM entities like contacts, deals, or leads to capture extra data relevant to your business processes.
- Defining list-type properties with predefined values to standardize input.
- Configuring properties with specific types (e.g., string, number, date) and behaviors (required, multiple values allowed).
For example, you might add a "Customer Priority" property of type List with values "High, Medium, Low" to a contact entity to help segment customers.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2, Webhook URL, or API Key authentication. |
| Property Name | The display name of the new entity item property to add. |
| Property Code | The internal code identifier for the 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 be filled in (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 possible values. |
Output
The node outputs JSON data representing the result of the operation performed on Bitrix24. This typically includes confirmation of the property addition or details about any errors encountered.
If the operation fails but the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with metadata such as the resource name and timestamp.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Relies on Bitrix24 API endpoints to perform operations; thus, network connectivity and proper API permissions are necessary.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
Common Issues:
- Incorrect or expired authentication credentials leading to authorization failures.
- Invalid property codes or names causing API rejections.
- Attempting to add properties with unsupported types or malformed property values.
- Network issues preventing communication with Bitrix24 API.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield if "continue on fail" is enabled. - Typical messages may indicate invalid parameters, permission denied, or rate limiting.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolutions:
- Verify and refresh authentication credentials.
- Ensure property codes conform to Bitrix24 naming rules.
- Validate property values especially for list types (comma-separated strings).
- Check network connectivity and API access rights.