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 platform, specifically focusing on its CRM and business management capabilities. The "Data Storage" resource with the "Update Item" operation allows users to update existing items (entities) within Bitrix24, such as leads, deals, contacts, or custom entities.
Typical use cases include:
- Updating CRM records automatically based on external triggers or workflows.
- Synchronizing data from other systems into Bitrix24.
- Modifying specific fields of an entity without manual intervention.
For example, a user might update a deal's status or a contact's phone number dynamically during a workflow execution.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used for authenticating API requests. Options: OAuth2 (recommended), Webhook (simpler), API Key. |
| Entity Type | The type of entity to update, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. |
| Item ID | The unique identifier of the item/entity to update. |
| Item Data | JSON object containing the fields and values to update on the item. Example: {"NAME": "New Name", "PROPERTY_VALUES": {}} |
| Options | Additional optional parameters: |
| - Access Token | Access token string for authentication override. |
| - Filter | JSON filter criteria (not typically used in update but available). |
| - Select | Comma-separated list of fields to select (mostly for retrieval operations). |
| - Order | JSON object defining order criteria (mostly for retrieval operations). |
| - Start | Number indicating start position for pagination (mostly for retrieval operations). |
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 item. The structure typically includes:
- Confirmation of the update operation.
- Updated fields and their new values.
- Any error messages if the update failed.
If the update fails and the node is configured to continue on failure, the output will contain an error object with details including the error message, resource name, and timestamp.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to perform entity updates.
- Uses internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect entity type or item ID causing "item not found" errors.
- Malformed JSON in the "Item Data" property resulting in request failures.
- Insufficient permissions for the authenticated user to update certain entities.
Error Messages:
"Failed to load CRM fields"or similar indicates issues fetching metadata; check connectivity and credentials.- Errors returned from Bitrix24 API are passed through; verify the correctness of entity type, item ID, and data format.
- If the node throws an error and "Continue On Fail" is disabled, the workflow will stop; enabling it can help handle errors gracefully.
Resolutions:
- Verify and refresh authentication credentials.
- Double-check entity type strings and item IDs.
- Validate JSON syntax in "Item Data".
- Ensure the authenticated user has sufficient rights in Bitrix24.