Actions31
- Company Actions
- Contact Actions
- Deal Actions
- Item Actions
- Lead Actions
- User Custom Method Actions
Overview
This node integrates with the Bitrix24 REST API to update a Deal record. It allows users to modify existing deal data by specifying the deal's unique ID and providing new values for one or more fields. This is useful in scenarios where you need to programmatically keep your CRM deals up-to-date based on external triggers or workflows, such as updating deal stages after a sales call or modifying deal details when new information arrives.
Practical examples:
- Automatically update the status of a deal after a payment confirmation.
- Change the assigned sales representative for a deal based on workload balancing.
- Modify custom fields in a deal when related customer data changes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24 API: either OAuth2 or Webhook-based authentication. |
| ID | The unique identifier of the deal record to update. |
| Input Type | How to provide the update data: - Using Fields: Specify individual field names and their new values. - Using JSON: Provide the entire update payload as raw JSON. |
| Fields | When using "Using Fields" input type, specify one or more fields to update: - Name or ID: Select the field to update. - Value: The new value to assign to that field. |
| JSON Body | When using "Using JSON" input type, provide the complete update data as a JSON object. |
Output
The node outputs the response from the Bitrix24 API after attempting to update the deal. The output is structured as JSON containing the updated deal data or an error message if the update failed.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the deal, but this node focuses on JSON data only.
Dependencies
- Requires access to the Bitrix24 REST API.
- Needs valid authentication credentials configured in n8n, either via OAuth2 or Webhook authentication methods.
- The node depends on internal methods to load available entity fields dynamically for user selection.
Troubleshooting
- Invalid ID Error: If the provided deal ID does not exist or is incorrect, the API will return an error. Verify the ID before running the node.
- Authentication Failures: Ensure that the selected authentication method is correctly configured and the credentials are valid.
- Malformed JSON: When using the JSON input type, invalid JSON syntax will cause errors. Validate JSON format before submission.
- Field Validation Errors: Providing invalid field names or incompatible values may result in API errors. Use the dynamic field loader to select valid fields.
- API Rate Limits: Frequent updates might hit Bitrix24 API rate limits; consider adding delays or error handling for retries.
Links and References
- Bitrix24 REST API Documentation
- n8n Expressions Documentation (for dynamic field IDs)