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 node integrates with the Bitrix24 platform, specifically focusing on its Data Storage resource for the "Count" operation. It allows users to count entities stored in Bitrix24 based on specified filter criteria and options. This is useful when you want to quickly determine how many records meet certain conditions without retrieving all data.
Common scenarios include:
- Counting CRM contacts or deals that match specific filters.
- Getting the number of leads created within a date range.
- Determining how many items exist in a custom Smart Process Automation (SPA) entity.
Practical example: You want to know how many active deals are currently assigned to a particular sales representative. Using this node, you can specify the filter for the assigned user and get the count directly.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key. |
| Options | Collection of optional parameters to refine the count query: |
| - Access Token | Access token string for authentication (used if applicable). |
| - Filter | JSON object defining filter criteria to select which records to count. |
| - Select | Comma-separated list of fields to select (not typically relevant for count but available). |
| - Order | JSON object specifying order criteria (usually irrelevant for count but present). |
| - Start | Number indicating the start position for pagination (mostly unused in count context). |
Output
The output contains a JSON object with the count result of the queried entities matching the filter criteria. The exact structure depends on the Bitrix24 API response but generally includes:
json: An object containing the count value and possibly metadata.- If an error occurs and "Continue On Fail" is enabled, the output will contain an error message, the resource name, and a timestamp.
No binary data output is expected from 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 corresponding to the chosen authentication method.
- Relies on Bitrix24 API endpoints to perform the count operation.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid tokens or keys.
- Filter syntax issues: The filter property expects valid JSON; malformed JSON will cause errors.
- API limits or permissions: Insufficient permissions or API rate limits may cause failures.
- Empty or unexpected results: Verify that the filter criteria actually match existing records.
- Error messages: If the node throws errors, enabling "Continue On Fail" will provide error details in the output JSON for easier debugging.