Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage Lead records. Specifically, the "Update" operation allows users to modify existing Lead entries by specifying the Lead's ID and the fields to update. This is useful in scenarios where you need to keep your CRM data current, such as updating contact information, lead status, or custom attributes after receiving new information from other systems or user input.
Practical examples include:
- Automatically updating a lead’s status when a related event occurs.
- Changing contact details based on form submissions.
- Modifying custom fields to reflect new business logic or sales stages.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Lead record to update. |
| Fields | A collection of fields to update on the Lead. Each field consists of: |
| - Field Name: The name of the Lead field to update (loaded dynamically from Bitrix24). | |
| - Field Value: The new value to assign to the specified field. |
Output
The node outputs an array of JSON objects representing the response from the Bitrix24 API for each updated Lead record. Each object typically contains the result of the update operation, including success confirmation or error details if the update failed.
If multiple items are processed, the output will be an array of these response objects corresponding to each input item.
Dependencies
- Requires an active Bitrix24 API connection configured with a valid webhook URL.
- The webhook URL must have permissions to access and modify Lead records.
- Uses HTTP POST requests to Bitrix24 REST API endpoints specific to the Lead resource.
Troubleshooting
- Missing Credentials or Webhook URL: The node throws errors if credentials or the webhook URL are not provided. Ensure that the API key or authentication token and webhook URL are correctly set up in n8n credentials.
- Invalid Field Names: If a field name does not exist or is read-only in Bitrix24, the update may fail. Use the dynamic field loader to select valid fields.
- API Errors: Network issues or permission problems can cause API call failures. Check the webhook URL accessibility and user permissions in Bitrix24.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output for failed items.