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
The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform. Specifically, the Data Storage - Update operation enables updating existing entities within Bitrix24, such as leads, deals, contacts, or custom entities. This is useful for automating updates to CRM records based on external triggers or workflows, ensuring data consistency and reducing manual entry.
For example, you could use this node to update a CRM lead's status after a customer interaction or modify deal details when new information becomes available.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Entity Type | The type of entity to update, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. |
| Entity ID | The unique identifier of the entity record to update. |
| Entity Data | JSON object containing the fields and values to update on the entity, e.g., {"NAME": "New Name"}. |
| Options | Additional optional parameters: - Access Token: token string for authentication - Filter: JSON filter criteria - Select: comma-separated list of fields to select - Order: JSON order criteria - Start: pagination start position |
Output
The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after attempting to update the specified entity. The structure typically includes confirmation of the update or error details if the update failed.
If the update is successful, the output JSON will contain updated entity data or status confirmation. If binary data were involved (not indicated here), it would be included in a separate binary property, but this node focuses on JSON data.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Needs proper configuration of these credentials in n8n.
- Relies on Bitrix24 API endpoints to perform entity updates.
Troubleshooting
- Common issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect entity IDs or entity types may result in "entity not found" errors.
- Malformed JSON in the Entity Data property can cause request failures.
- Error messages:
- Errors returned from Bitrix24 API are passed through; typical messages include authentication errors, validation errors on fields, or permission denials.
- Resolutions:
- Verify that authentication credentials are correct and have necessary permissions.
- Confirm the entity type and ID exist in Bitrix24.
- Ensure JSON syntax in Entity Data is valid and matches expected field formats.