Actions25
Overview
This node integrates with the Bitrix24 CRM system via its API, allowing users to perform various operations on CRM records such as leads, deals, contacts, and companies. Specifically, the Update operation enables updating an existing record by specifying its ID and the fields to modify.
Common scenarios for this node include:
- Automatically updating customer or deal information in Bitrix24 after receiving new data from other systems.
- Synchronizing external databases or forms with Bitrix24 records.
- Modifying specific fields of a CRM record based on workflow logic, e.g., changing status or adding notes.
Example: Update a lead's status and assigned user by providing the lead ID and the fields "STATUS_ID" and "ASSIGNED_BY_ID" with new values.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the record to update. Required for update, get, and delete operations. |
| Fields | A collection of fields to update on the record. Each field consists of: - Field Name: Selectable from available Bitrix24 CRM fields. - Field Value: The new value to set for that field. |
Output
The node outputs an array of JSON objects representing the responses from the Bitrix24 API for each input item processed.
For the Update operation, the output JSON typically contains:
- Confirmation of the update action.
- Possibly the updated record ID or status returned by Bitrix24.
No binary data is output by this node.
Dependencies
- Requires a valid Bitrix24 API webhook URL credential configured in n8n.
- Uses HTTP POST requests to Bitrix24 API endpoints constructed from the webhook URL and resource/operation paths.
- Relies on the Bitrix24 API being accessible and the webhook URL having sufficient permissions to perform updates.
Troubleshooting
- Missing Credentials: If no credentials or webhook URL are provided, the node will throw errors indicating these are required.
- Invalid Field Names or Values: Providing incorrect field names or invalid values may cause the Bitrix24 API to reject the update request.
- API Errors: Network issues or API limits can cause failures; error messages from the API are passed through.
- Continue On Fail: If enabled, the node will continue processing remaining items even if some fail, returning error details per item.
To resolve common errors:
- Ensure the webhook URL is correct and active.
- Verify field names against the Bitrix24 CRM fields (the node supports loading these dynamically).
- Check API permissions and rate limits.
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 CRM Fields Reference (for understanding field names and types)