Actions25
Overview
This node integrates with the Bitrix24 CRM system to update existing Deal records. It allows users to modify fields of a Deal by specifying the record ID and the new field values. The node supports two input formats for updating fields: a form-based interface where individual fields are specified, or a JSON string representing the fields to update.
Common scenarios include:
- Automating updates to deal information such as stage, amount, or custom fields based on external triggers.
- Synchronizing deal data from other systems into Bitrix24.
- Bulk updating deals in workflows by iterating over multiple inputs.
Example use case:
- A workflow receives updated sales data and uses this node to update corresponding deals in Bitrix24 with new amounts and statuses.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Deal record to update. |
| Input Format | Method to provide fields for update: - Form: Specify each field individually. - JSON: Provide all fields as a JSON object string. |
| Fields (JSON) | JSON string representing the fields and their new values to update (used when Input Format is JSON). |
| Fields | Collection of fields to update (used when Input Format is Form). Each entry includes: - Field Name: The name of the Deal field to update. - Communication Type: For contact-related fields like phone/email, specify type (e.g., Work, Mobile). - Field Value: The new value for the field; can be a string or an enumeration depending on the field type. |
Output
The node outputs an array of JSON objects representing the response from Bitrix24 API for each processed input item. For the Update operation, the output typically contains the result of the update request, including success status and any returned data from Bitrix24.
No binary data output is produced by this node.
Dependencies
- Requires a valid Bitrix24 API authentication credential configured in n8n.
- Needs the Bitrix24 webhook URL to access the CRM API endpoints.
- Uses HTTP POST requests to Bitrix24 REST API endpoints for updating records.
- The node dynamically fetches metadata about Deal fields from Bitrix24 to support dynamic field selection and validation.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if the API credentials or webhook URL are not set or invalid. Ensure that the Bitrix24 API credential is properly configured and includes a valid webhook URL.
- Invalid JSON in Fields (JSON): When using JSON input format, malformed JSON will cause parsing errors. Validate JSON syntax before running the node.
- Field Names Not Found: If a specified field name does not exist in Bitrix24 or is misspelled, the update may fail or ignore those fields. Use the dynamic field loader to select valid fields.
- API Errors: Network issues or permission problems in Bitrix24 can cause API call failures. Check API permissions and network connectivity.
- Continue On Fail Behavior: If enabled, the node will continue processing remaining items even if some updates fail, returning error messages per failed item.
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 CRM Deals API Reference
- n8n documentation on Creating Custom Nodes