Bitrix24

Overview

This node integrates with the Bitrix24 CRM and business platform, specifically enabling operations on data storage entities within Bitrix24. The "Add Item" operation under the "Data Storage" resource allows users to create new items (records) in specified entity types such as leads, deals, contacts, or custom entities.

Common scenarios for this node include:

• Automating the creation of CRM records when a new lead is captured from a web form.
• Adding new deals or contacts programmatically based on external triggers.
• Integrating Bitrix24 with other systems by pushing data into Bitrix24 entities automatically.

For example, you could use this node to add a new CRM lead with specific properties like name, email, and phone number whenever a new customer inquiry is received via another system.

Properties

Output

The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after adding the item. This typically includes details of the newly created record such as its ID and any other returned metadata.

If an error occurs and the node is configured to continue on failure, the output will contain an 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 appropriate permissions.
• Needs one of the following authentication methods configured in n8n:
  • OAuth2 credentials for secure production use.
  • Webhook URL for simpler but less secure access.
  • API key credential for direct API access.
• The node internally uses Bitrix24 API endpoints to perform operations.

Troubleshooting

• Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
• Invalid entity type: The Entity Type must be a valid Bitrix24 entity identifier. Using an incorrect or unsupported entity type will cause API errors.
• Malformed JSON in Item Data: The Item Data field must be valid JSON matching the expected structure for the entity. Invalid JSON or missing required fields can cause failures.
• API rate limits or connectivity issues: Network problems or hitting Bitrix24 API limits may result in errors. Retrying or checking network status can help.
• Error messages: If the node throws errors, they usually include the API error message. Enabling "Continue On Fail" can help capture these errors in the workflow for debugging.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 CRM Entities Guide
• n8n Documentation on Creating Custom Nodes