Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically focusing on telephony features. The "Register External Call" operation allows users to register an external phone call within Bitrix24's telephony system. This is useful for logging calls made or received outside of Bitrix24 but that should be tracked in the CRM for record-keeping, analytics, or automation purposes.

Common scenarios include:

• Logging calls from third-party telephony systems into Bitrix24.
• Tracking incoming and outgoing calls made via external lines.
• Associating calls with specific users in Bitrix24.
• Differentiating call types such as incoming, outgoing, callback, or outgoing with number substitution.

Practical example:
A company uses a separate VoIP provider for calls but wants all call records to appear in Bitrix24 CRM. Using this node, each call can be registered automatically with details like phone number, user ID, call type, and line number, ensuring consistent call history across platforms.

Properties

Output

The node outputs JSON data representing the result of the call registration request to Bitrix24. This typically includes confirmation of the call registration and any relevant metadata returned by the Bitrix24 API.

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.

The node does not output binary data.

Dependencies

• Requires access to a Bitrix24 account with telephony enabled.
• Requires one of the following authentication methods configured in n8n:
  • OAuth2 credentials for Bitrix24.
  • A Bitrix24 webhook URL.
  • An API key credential for Bitrix24.
• Network connectivity to Bitrix24 API endpoints.

Troubleshooting

• Authentication errors: Ensure the selected authentication method is correctly configured and valid. OAuth2 tokens may expire and need refreshing.
• Invalid phone numbers: Verify the phone number format matches Bitrix24 requirements.
• User ID issues: The specified user ID must exist in Bitrix24; otherwise, the call may not associate properly.
• Call type mismatches: Use the correct call type value to avoid unexpected behavior.
• API rate limits or connectivity problems: Check network access and Bitrix24 API usage limits.
• Error messages in output: If the node returns an error in the JSON output, review the error message for clues and verify input parameters.

Links and References

• Bitrix24 Telephony API Documentation
• Bitrix24 Official Website
• n8n Documentation on Credentials