Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform. Specifically, for the Data Storage resource and the Add Section operation, this node enables users to add a new section to a specified entity type within Bitrix24. This is useful when organizing CRM data into logical sections or categories, such as grouping leads, deals, or contacts under custom sections.
Common scenarios include:
- Structuring CRM entities by adding custom sections to better organize records.
- Automating the creation of sections during data import or synchronization workflows.
- Enhancing CRM customization by programmatically managing entity sections.
Example: Adding a new section named "VIP Clients" with a specific code to the CRM_LEAD entity type.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key. |
| Entity Type | The type of entity to which the section will be added. Examples: CRM_LEAD, CRM_DEAL, CRM_CONTACT. |
| Section Data | JSON object containing the data for the new section, e.g., {"NAME": "Section Name", "CODE": "section_code"}. |
| Options | Additional optional parameters: - Access Token: token string for authentication - Filter: JSON filter criteria - Select: comma-separated fields to select - Order: JSON order criteria - Start: pagination start position |
Output
The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to add the section. The structure typically includes details about the newly created section such as its ID and any metadata returned by the Bitrix24 API.
If an error occurs and the node is configured to continue on failure, the output will contain an error message along with the resource name and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, Webhook URL, or API Key.
- Uses Bitrix24 API endpoints internally to perform operations.
- No additional external dependencies beyond standard n8n credential management and HTTP request capabilities.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
- Invalid entity type: The entity type must be a valid Bitrix24 CRM entity (e.g., CRM_LEAD). Using an unsupported or misspelled entity type will cause failures.
- Malformed section data: The
sectionDataproperty must be a valid JSON object with required fields likeNAME. Invalid JSON or missing required fields will result in API errors. - API rate limits or connectivity issues: Network problems or Bitrix24 API limits may cause errors; retry or check API status.
- Error messages: If the node throws errors, they will include the message from Bitrix24's API response. Use these messages to adjust input parameters or authentication.