Bitrix24 Auxiliary icon

Bitrix24 Auxiliary

Управление вспомогательными сущностями в Bitrix24

Actions10

Overview

This node interacts with Bitrix24 CRM to manage sales funnel statuses ("Статус воронки") and categories ("Воронка продаж"). Specifically, the "Get All" operation for the "Статус воронки" resource retrieves all status elements associated with a given sales funnel category. This is useful when you want to list or process all stages/statuses of a particular sales funnel in Bitrix24, for example, to display them in a dashboard, synchronize with another system, or automate workflows based on funnel stages.

Practical examples:

  • Fetching all deal stages (statuses) within a specific sales funnel to analyze pipeline health.
  • Synchronizing Bitrix24 sales funnel statuses with an external reporting tool.
  • Automating notifications or actions triggered by changes in any funnel status.

Properties

Name Meaning
Category ID The unique identifier of the sales funnel (воронка продаж) whose statuses you want to retrieve. This property is required for the "Get All" operation on the "Статус воронки" resource.

Output

The output is a JSON array where each element represents a status in the specified sales funnel category. Each status object typically includes fields such as:

  • ID (status identifier)
  • NAME (name of the status)
  • SORT (sorting order)
  • COLOR (HEX color code representing the status)
  • SEMANTIC_INFO (semantic code indicating the type of status, e.g., Process, Success, Failure)
  • CATEGORY_ID (the sales funnel category ID)
  • ENTITY_ID (entity identifier related to the funnel stage)
  • STATUS_ID (a composite ID combining category and sort)

No binary data output is produced by this node.

Dependencies

  • Requires an active Bitrix24 API connection via a webhook URL credential.
  • The node uses HTTP POST requests to Bitrix24's webhook endpoints to perform API calls.
  • The user must configure the node with valid Bitrix24 API credentials that include a webhook URL.
  • Optionally, the node respects a language setting from credentials to set the default language environment variable.

Troubleshooting

  • Missing Credentials or Webhook URL: The node will throw errors if no credentials are provided or if the webhook URL is missing. Ensure the Bitrix24 API credential is properly configured with a valid webhook URL.
  • API Errors: If Bitrix24 returns an error, the node surfaces the error description. Common issues include invalid category IDs or insufficient permissions.
  • Empty Results: If the category ID does not exist or has no statuses, the output may be empty. Verify the category ID correctness.
  • Network Issues: Connectivity problems to Bitrix24 webhook URLs can cause request failures.
  • Continue On Fail: If enabled, the node collects errors per item instead of stopping execution, which helps in batch processing scenarios.

Links and References

Discussion