Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically providing access to telephony-related data. The "Get Voximplant Statistics" operation retrieves call statistics from a specified telephony line within a given date range. This is useful for monitoring call activity, analyzing call volumes, and generating reports on telephony usage.

Practical scenarios include:

  • Tracking call performance metrics for a specific phone line.
  • Generating daily or weekly call statistics for management reporting.
  • Filtering and sorting call data to analyze peak usage times or call outcomes.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Line ID The unique identifier of the telephony line for which statistics are requested.
Date From The start date/time for the statistics query (inclusive).
Date To The end date/time for the statistics query (inclusive).
Additional Options Optional parameters including:
• Filter: JSON object to filter results.
• Sort: JSON object defining sort order.
• Start: Number indicating pagination start position.

Output

The node outputs an array of items where each item's json property contains the retrieved Voximplant statistics data for the specified line and date range. The exact structure depends on the Bitrix24 API response but typically includes call counts, durations, statuses, and other relevant telephony metrics.

If the node supports binary data output (not explicitly shown in the provided code), it would represent any associated media or files related to calls, such as recordings.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2 token, webhook URL, or API key).
  • Access to the Bitrix24 telephony API endpoints.
  • Proper configuration of the node's credentials in n8n to enable authenticated API calls.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials will cause API call failures.
    • Incorrect or missing Line ID will result in errors or empty responses.
    • Date range parameters outside allowed limits may cause no data to be returned.
    • Malformed JSON in the filter or sort options can lead to request errors.

  • Error Messages:

    • Errors thrown by the node include the error message from the Bitrix24 API.
    • If continueOnFail is enabled, errors are returned as part of the output JSON with an error field describing the issue.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the Line ID corresponds to an existing telephony line.
    • Validate date inputs and JSON formatting for filters and sorting.
    • Check network connectivity and Bitrix24 service status.

Links and References

Discussion