Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage "Deal" records. Specifically, the Update operation allows users to modify existing deal entries by specifying the record ID and the fields to update. This is useful in scenarios where deal information changes over time, such as updating the deal stage, amount, or custom properties after new information is received.
Practical examples include:
- Updating the status of a sales deal after a client meeting.
- Changing the expected close date based on new timelines.
- Modifying custom fields like priority or assigned salesperson.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the deal record to update. |
| Fields | A collection of fields to update on the deal. Each field consists of: |
| - Field Name: The name of the deal property 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 deal. Typically, this includes confirmation of the update operation and may contain the updated deal data or status messages.
No binary data output is produced by this operation.
Dependencies
- Requires a valid Bitrix24 API webhook URL credential configured in n8n.
- Uses HTTP POST requests to Bitrix24's REST API endpoints specific to the "deal" resource.
- The webhook URL must have permissions to update deal records.
Troubleshooting
- Missing Credentials: If the API credentials or webhook URL are not set or invalid, the node will throw an error indicating that no credentials were returned or the webhook URL is required.
- Invalid Deal ID: Providing a non-existent or incorrect deal ID will cause the API to return an error; ensure the ID corresponds to an existing deal.
- Field Names: Using incorrect or unsupported field names may result in update failures. Use the dynamic field loader to select valid fields.
- API Errors: Network issues or permission problems can cause request failures. Check API access rights and network connectivity.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning error details in the output.
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 Deals API Reference
- n8n Documentation on Creating Custom Nodes