Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically to retrieve all statuses related to a chosen entity in Bitrix24 CRM or business processes. The "Get All Statuses" operation under the "Status" resource fetches multiple status entries, potentially paginated, allowing users to obtain comprehensive lists of statuses such as deal stages, lead statuses, or other entity-specific status sets.

Common scenarios include:

  • Synchronizing Bitrix24 status lists with external systems.
  • Displaying available status options for CRM entities in custom workflows.
  • Automating reporting or analytics based on status distributions.

For example, a user might want to fetch all deal stages (statuses) to populate a dropdown in a form or to analyze how many deals are in each stage.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key authentication
Return All Whether to return all results or only a subset. If false, limits the number of pages loaded.
Max Pages to Load Maximum number of pages to load when Return All is false. Each page contains up to 50 items.
Options Additional filtering and customization options:
- Entity ID: Filter by specific entity status type (e.g., DEAL_STAGE, LEAD_STATUS)
- Filter: JSON object defining filter criteria
- Order: JSON object defining sort order
- Select Fields: Comma-separated list of fields to return
- Language: Language code for localized names
- Custom Parameters: Additional parameters as JSON object

Output

The node outputs an array of status objects in the json field of each item. Each object represents a status entry corresponding to the specified entity and filters. The structure typically includes status identifiers, names, and possibly localized labels depending on the language parameter.

If pagination is involved and Return All is true, the output will contain all pages concatenated into one array.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
  • Needs proper configuration of credentials in n8n for the selected authentication method.
  • Relies on Bitrix24 API endpoints that provide status information for CRM entities.

Troubleshooting

  • Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
  • Empty results: Verify that the Entity ID option matches a valid Bitrix24 entity status type (e.g., DEAL_STAGE). Also, check filter criteria if used.
  • Pagination limits: If not all statuses appear, consider increasing Max Pages to Load or enabling Return All.
  • Invalid JSON in filter/order/custom parameters: Make sure JSON inputs are well-formed; otherwise, the API call may fail.
  • API rate limits or connectivity issues: Check network access and Bitrix24 API usage quotas.

Links and References

Discussion