Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically providing operations related to telephony features. The "Hide External Call" operation allows users to programmatically hide an external call in Bitrix24's telephony system. This can be useful in scenarios where calls need to be managed or controlled automatically, such as hiding certain calls from appearing in call logs or user interfaces based on custom business logic.

Practical examples include:

  • Automatically hiding calls that are identified as spam or robocalls.
  • Managing call visibility during automated workflows or CRM processes.
  • Controlling call display for privacy or compliance reasons within a sales or support team.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Call ID The unique identifier of the call to be hidden. Required to specify which call to affect.

Output

The node outputs JSON data representing the result of the operation. In case of success, it typically returns the response from Bitrix24 confirming the call was hidden. If an error occurs, the output JSON includes an error field with the error message, the resource name ("telephony"), and a timestamp indicating when the error happened.

No binary data output is involved in this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
  • The node depends on Bitrix24's telephony API endpoints to perform the hide call action.
  • Proper configuration of the Bitrix24 credentials in n8n is necessary for successful API communication.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials will cause API calls to fail.
    • Providing an incorrect or non-existent Call ID will result in errors or no effect.
    • Network connectivity issues may prevent communication with Bitrix24 servers.

  • Error Messages:

    • Errors returned from Bitrix24 API will be included in the output JSON under the error field.
    • Typical messages might indicate authentication failure, invalid parameters, or permission issues.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the Call ID is correct and corresponds to an active call.
    • Check network access and firewall settings.
    • Enable "Continue On Fail" in the node settings if you want the workflow to proceed despite errors.

Links and References

Discussion