Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically focusing on telephony-related operations. The "Attach Call Record" operation allows users to attach a recording file URL to a specific call identified by its Call ID. This is useful in scenarios where call recordings are stored externally or generated by third-party systems and need to be linked back to the corresponding call record within Bitrix24 for tracking, auditing, or CRM purposes.

Practical examples:

• Automatically attaching recorded customer support calls to their respective call logs in Bitrix24.
• Linking external call recordings from a telephony provider to Bitrix24 call records for unified access.
• Archiving sales call recordings by associating them with the correct call entries in Bitrix24.

Properties

Output

The node outputs JSON data representing the result of the operation. Typically, this includes confirmation that the call record was successfully attached or error information if the operation failed.

If an error occurs and the node is configured to continue on failure, 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 indicated for this operation.

Dependencies

• Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
• The node depends on Bitrix24's API endpoints to perform telephony operations.
• Proper configuration of the chosen authentication method in n8n is necessary for successful API calls.

Troubleshooting

• Common issues:

  • Invalid or expired authentication credentials leading to authorization errors.
  • Incorrect Call ID resulting in failure to find the call to attach the recording.
  • Malformed or inaccessible Record URL causing the attachment to fail.

• Error messages:

  • Errors returned from Bitrix24 API will be surfaced in the node's output under the error field if "Continue On Fail" is enabled.
  • Typical errors include authentication failures, invalid parameters, or network connectivity issues.

• Resolutions:

  • Verify and refresh authentication credentials.
  • Confirm the Call ID exists and is correct.
  • Ensure the Record URL is publicly accessible or accessible by Bitrix24.
  • Check network connectivity and API endpoint availability.

Links and References

• Bitrix24 Telephony API Documentation
• Bitrix24 API Authentication Methods