Bitrix icon

Bitrix

Consume Bitrix24 REST API

Actions31

Overview

This node integrates with the Bitrix24 CRM system to update an existing CRM item record. It allows users to modify fields of a specified CRM entity by providing either individual field values or a raw JSON object representing the updated data. This is useful in automation workflows where CRM records need to be programmatically updated based on external triggers or data changes, such as updating deal information after a payment confirmation or modifying contact details from a form submission.

Properties

Name Meaning
Authentication Method of authentication to use for connecting to Bitrix24: either OAuth2 or Webhook.
Entity Type Name or ID Identifier of the CRM entity type to update (e.g., Lead, Deal, Contact). Can be selected from a list or provided as an expression.
ID The unique identifier of the specific CRM record to update.
Input Type How to provide the update data: "Using Fields" to specify individual fields and their values, or "Using JSON" to provide a complete JSON body with all data.
Fields When using "Using Fields" input type, this collection allows specifying multiple field name-value pairs to update. Field names can be selected from a dynamic list depending on the entity type.
JSON Body When using "Using JSON" input type, this property accepts a raw JSON object representing the full data to update on the CRM record.
Use Original UF Names Boolean option to decide whether to use original custom field names prefixed with UF_CRM when updating custom fields.

Output

The node outputs the response from the Bitrix24 API after attempting to update the CRM item. The output is structured as JSON containing the updated record's data or status information returned by the API. If the update is successful, the output typically includes the updated fields and identifiers confirming the change. There is no indication that binary data is handled by this node.

Dependencies

  • Requires connection to Bitrix24 REST API.
  • Needs either OAuth2 credentials or a Webhook URL configured in n8n for authentication.
  • Dynamic loading of entity types and fields depends on Bitrix24 API responses.
  • No other external dependencies are indicated.

Troubleshooting

  • Common issues:

    • Incorrect or missing record ID will cause the update to fail.
    • Providing invalid field names or values not matching the entity schema may result in API errors.
    • Authentication failures if OAuth2 tokens expire or webhook URLs are incorrect.
    • Using JSON input with malformed JSON will cause parsing errors.

  • Error messages and resolutions:

    • "Record not found" — Verify the ID corresponds to an existing record in Bitrix24.
    • "Invalid field name" — Check that field names match those available for the selected entity type.
    • "Authentication failed" — Reconfigure credentials or refresh OAuth2 tokens.
    • "Malformed JSON" — Validate JSON syntax before submitting.

Links and References

Discussion