Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
This node integrates with the Bitrix24 CRM and business platform, allowing users to perform various operations on Bitrix24 resources. Specifically, for the Data Storage > Add operation, it enables creating new entities within Bitrix24, such as leads, deals, contacts, or other CRM objects.
Common scenarios where this node is beneficial include:
- Automating the creation of CRM records from external data sources.
- Integrating form submissions or other app events directly into Bitrix24.
- Streamlining business workflows by programmatically adding new entities without manual entry.
For example, a marketing automation workflow could use this node to add new leads to Bitrix24 whenever a visitor fills out a web form.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: • OAuth2 (recommended for production) • Webhook (simpler but less secure) • API Key authentication |
| Entity Type | The type of entity to create in Bitrix24, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. This determines which kind of record will be added. |
| Entity Data | JSON object containing the data fields and values for the new entity. For example: json { "NAME": "Entity Name", "ACTIVE": "Y" } |
| Options | Additional optional parameters: • Access Token: string token for authentication • Filter: JSON filter criteria (not typically used for add operation) • Select: Comma-separated list of fields to select • Order: JSON order criteria • Start: Number for pagination start position |
Output
The node outputs an array of items, each containing a json property representing the response from Bitrix24 after attempting to add the entity. The structure typically includes:
- Details of the created entity, such as its ID and any returned fields.
- In case of failure, an error message may be included in the output JSON under an
errorkey.
If binary data were involved (not typical for this operation), it would be summarized accordingly, but this node primarily handles JSON data related to CRM entities.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
- Relies on Bitrix24's REST API endpoints to perform entity creation.
- No additional external libraries beyond those bundled are required.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens. OAuth2 requires proper token refresh handling.
- Invalid entity type: If the specified entity type does not exist or is misspelled, the API call will fail. Verify the exact entity type strings supported by your Bitrix24 instance.
- Malformed entity data: The JSON provided in
Entity Datamust conform to Bitrix24's expected schema for the entity type. Invalid or missing required fields will cause errors. - API rate limits or connectivity issues: Network problems or Bitrix24 API limits can cause failures. Check network access and consider retry logic if needed.
- Error messages: The node returns error details in the output JSON when
continueOnFailis enabled. Review these messages to identify issues.