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 integrates with the Bitrix24 CRM and business platform, enabling users to interact programmatically with various Bitrix24 resources. Specifically, the Data Storage - Get Sections operation retrieves sections related to a specified entity type within Bitrix24.
This node is beneficial in scenarios where you need to dynamically fetch organizational or categorization structures (sections) for entities such as leads, deals, contacts, or custom CRM entities. For example, you might want to list all deal stages or contact groups before processing or filtering data further in your workflow.
Practical examples include:
- Fetching all sections of CRM leads to display or process them.
- Retrieving sections for custom Smart Process Automation (SPA) entities to automate workflows based on section membership.
- Using the sections data to populate dropdowns or selection lists in subsequent nodes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: • OAuth2 (recommended for production) • Webhook (simpler but less secure) • API Key authentication |
| Entity Type | The type of entity to work with, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. This defines which entity's sections will be retrieved. |
| Return All | Whether to return all available results or limit the output to a certain number. If false, only up to a given limit will be returned. |
| Options | Additional optional parameters: • Access Token: A string token for authentication. • Filter: JSON object defining filter criteria to narrow down results. • Select: Comma-separated list of fields to retrieve. • Order: JSON object specifying sorting order. • Start: Number indicating the start position for pagination. |
Output
The node outputs an array of JSON objects representing the sections retrieved from Bitrix24 for the specified entity type. Each item in the output corresponds to one section and contains its properties as returned by the Bitrix24 API.
The exact structure depends on the Bitrix24 API response but typically includes identifiers, names, and metadata about each section.
If the node supports binary data output (not indicated explicitly here), it would represent any associated files or attachments related to sections, but this operation primarily deals with JSON data.
Dependencies
- Requires connection to a Bitrix24 instance via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
- Relies on Bitrix24 API endpoints to fetch entity sections.
- No additional external libraries beyond those bundled with the node are required.
Troubleshooting
- Authentication Errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens. OAuth2 requires a valid access token; webhooks require a correct URL; API keys must be active.
- Invalid Entity Type: If the entity type is incorrect or unsupported, the API call may fail or return empty results. Verify the entity type string matches Bitrix24's expected values.
- Empty Results: If no sections are returned, check if the entity actually has defined sections or if filters applied exclude all results.
- API Rate Limits: Bitrix24 may impose rate limits; excessive calls can lead to temporary blocking. Implement retries or reduce request frequency if needed.
- Error Messages: The node returns error details in the output JSON when
continueOnFailis enabled. Common messages relate to network issues, invalid parameters, or authentication failures. Review these messages to adjust inputs or credentials accordingly.