Bitrix24

Overview

This node integrates with the Bitrix24 CRM system, allowing users to perform various operations on CRM resources such as Leads, Deals, Contacts, and Companies. Specifically, for the Company resource with the Get operation, the node retrieves a single company record by its ID. Users can optionally specify which fields of the company record they want to retrieve.

Common scenarios where this node is beneficial include:

• Fetching detailed information about a specific company stored in Bitrix24.
• Retrieving only selected fields to optimize data transfer and processing.
• Integrating Bitrix24 company data into workflows for reporting, notifications, or further automation.

Practical example:

• A workflow that triggers when a new deal is created and needs to fetch the associated company's details (e.g., name, industry, contact info) to enrich the deal data or send personalized communications.

Properties

Output

The node outputs an array of JSON objects representing the retrieved company records. For the Get operation, each object corresponds to one company and contains the requested fields as key-value pairs.

Example output structure for a single company might look like:

{
  "result": {
    "ID": "123",
    "TITLE": "Example Company",
    "ADDRESS": "123 Main St",
    "PHONE": "+1234567890"
    // other selected fields...
  }
}

No binary data output is produced by this node.

Dependencies

• Requires a valid Bitrix24 API authentication credential configured in n8n, providing access to the Bitrix24 webhook URL.
• Uses HTTP POST requests to Bitrix24's REST API endpoints via the webhook URL.
• The node dynamically loads available fields for selection from the Bitrix24 API.

Troubleshooting

• Missing Credentials or Webhook URL: The node will throw errors if the Bitrix24 API credentials or webhook URL are not set or invalid. Ensure credentials are properly configured.
• Invalid ID: Providing an incorrect or non-existent company ID will result in an error or empty response. Verify the ID before running the node.
• Field Selection Issues: Selecting fields that do not exist or are not accessible may cause errors. Use the dynamic field loader to select valid fields.
• API Errors: Network issues or Bitrix24 API downtime can cause request failures. Check connectivity and Bitrix24 service status.
• Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error messages per item.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 CRM Entities
• n8n Documentation - Creating Custom Nodes