Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically supporting various resources and operations including telephony features. For the Telephony resource and the Get Voximplant SIP Line operation, it retrieves details about a specific Voximplant SIP line by its ID.

Typical use cases include:

  • Fetching configuration or status information of a Voximplant SIP line integrated into Bitrix24 telephony.
  • Automating telephony management workflows where SIP line details are needed for further processing or decision-making.
  • Integrating telephony data into CRM or other business processes within Bitrix24.

Example: A user wants to get the current settings or status of a particular SIP line used for inbound/outbound calls in their Bitrix24 telephony system to display or log this information elsewhere.

Properties

Name Meaning
Authentication Method to authenticate API requests:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key (Bitrix24 API key authentication)
Line ID The unique identifier of the Voximplant SIP line to retrieve information for. This is required.

Output

The node outputs JSON data representing the details of the requested Voximplant SIP line. The exact structure depends on the Bitrix24 API response but typically includes properties such as line configuration, status, and related metadata.

If an error occurs during execution, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.

No binary data output is produced by this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
  • The node relies on Bitrix24's REST API endpoints to fetch telephony and SIP line data.
  • Proper permissions in Bitrix24 are necessary to access telephony and Voximplant SIP line information.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials leading to authorization errors.
    • Incorrect or non-existent Line ID causing "not found" errors.
    • Network connectivity problems preventing API calls.
  • Error messages:

    • Errors returned from Bitrix24 API will be included in the output JSON under the error field.
    • If the node is configured to continue on failure, it returns the error info instead of stopping execution.
  • Resolutions:

    • Verify that the authentication method and credentials are correctly set up and have sufficient permissions.
    • Double-check the Line ID value to ensure it corresponds to an existing Voximplant SIP line.
    • Ensure network access to Bitrix24 API endpoints is available.

Links and References

Discussion