Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to add custom user fields to Bitrix24 entities. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, making it flexible for different security and deployment scenarios.

A common use case is when a business wants to extend the default data model of Bitrix24 CRM entities (like contacts, deals, or leads) by adding custom fields to capture additional information relevant to their processes. For example, a sales team might add a "Customer Priority" field to deals to better track high-value clients.

Properties

Output

The node outputs an array of items where each item contains a json object representing the result of the add user field operation. If an error occurs and the node is configured to continue on failure, the output will include an error message along with the resource name and a timestamp.

The output JSON structure typically includes:

• Success response data from Bitrix24 about the created user field.
• In case of failure (with continueOnFail enabled), an error object with:
  • error: Error message string.
  • resource: The resource name involved.
  • timestamp: ISO string of the error occurrence time.

No binary data output is indicated in the source code.

Dependencies

• Requires connection to Bitrix24 API.
• Needs one of the following authentication credentials configured in n8n:
  • OAuth2 credential with valid access token.
  • Webhook URL credential.
  • API key credential.
• Uses internal helper functions to make standard Bitrix24 API calls.

Troubleshooting

• Common issues:
  • Invalid or expired access tokens causing authentication failures.
  • Insufficient permissions in Bitrix24 to add user fields.
  • Incorrect resource or operation parameters leading to API errors.
• Error messages:
  • Errors thrown during execution are caught and can be output if "Continue On Fail" is enabled.
  • Typical error messages include authentication failures, missing required parameters, or API call failures.
• Resolution tips:
  • Verify that the chosen authentication method is correctly set up and tokens are valid.
  • Ensure the Bitrix24 user has permission to modify user fields.
  • Double-check input parameters for correctness.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 Custom Fields Guide
• n8n Documentation on Credentials