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 new entities within the "Data Storage" resource. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, making it flexible for different security requirements.
Typical use cases include automating the creation of custom data entities in Bitrix24 CRM or business processes, such as adding new records for contacts, deals, or other custom entities managed within Bitrix24's data storage system. For example, a user might automate adding a new customer entity whenever a form is submitted on their website, or create a new deal entity when a sales opportunity arises.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook, or API Key. |
| Entity Name | The name of the entity to be added. |
| Entity Code | A unique code identifier for the entity. |
| Entity Active | Boolean flag indicating whether the entity is active (true) or inactive (false). |
| Entity Sort Order | Numeric value defining the sort order priority of the entity (default is 100). |
| Entity Description | Text description providing additional details about the entity. |
Output
The node outputs an array of items where each item contains a json object representing the result of the add entity operation. The exact structure depends on the Bitrix24 API response but typically includes confirmation of the created entity and its properties.
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 add entities.
- Needs one of the supported authentication credentials configured in n8n:
- OAuth2 credential (recommended for production)
- Webhook URL credential
- API key credential
- Relies on Bitrix24 API endpoints to perform operations.
- No additional external dependencies beyond standard HTTP requests to Bitrix24.
Troubleshooting
Common Issues:
- Authentication failures due to incorrect or expired credentials.
- Insufficient permissions in Bitrix24 to add entities.
- Invalid or missing required fields like Entity Name or Entity Code.
- Network connectivity issues preventing API calls.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Typical errors include authorization errors, validation errors for entity fields, or API rate limits.
Resolutions:
- Verify that the selected authentication method is correctly configured and valid.
- Ensure the user account has rights to create entities in Bitrix24.
- Double-check all required input properties are provided and valid.
- Check network connectivity and retry if transient errors occur.