Actions20
Overview
This node manages custom user fields in Bitrix24 CRM entities such as Leads, Deals, Contacts, and Companies. Specifically for the Company resource with the Update operation, it updates an existing custom field's properties like label, multiplicity, mandatory status, visibility in filters and lists, and enumeration list values if applicable.
Common scenarios include:
- Modifying the display name or label of a custom company field.
- Changing whether a field allows multiple values or is mandatory.
- Updating the list of selectable options for enumeration-type fields.
- Adjusting visibility settings for filtering and listing in the Bitrix24 UI.
Practical example: You have a custom dropdown field on companies representing "Industry Type" and want to update its label to "Primary Industry" and add new options to the dropdown list.
Properties
| Name | Meaning |
|---|---|
| Field ID | The unique identifier of the custom field to update. |
| Field Label | The display name (label) of the custom field shown in forms and lists. |
| List Values | For enumeration type fields only: the list of selectable values in the dropdown list. |
| Multiple | Whether the field supports multiple selections (true/false). |
| Mandatory | Whether the field is required to be filled (true/false). |
| Show Filter | Whether to show this field as a filter option in the UI (true/false). |
| Show In List | Whether to display this field in the list view of companies (true/false). |
Output
The node outputs an array of JSON objects corresponding to the API responses from Bitrix24 for each input item processed. For the update operation, the output typically contains confirmation of the update action or error details if the update failed.
Example output structure for a successful update:
{
"result": true,
"field": {
"id": "123",
"name": "UF_COMPANY_INDUSTRY",
"label": "Primary Industry",
...
}
}
If an error occurs during the update, the output will contain an error message object:
{
"error": "Error message describing what went wrong"
}
No binary data output is produced by this node.
Dependencies
- Requires an active Bitrix24 API webhook URL credential with permissions to manage CRM user fields.
- Uses HTTP POST requests via Axios to communicate with Bitrix24 REST API endpoints.
- The node expects the webhook URL to be provided in credentials.
- Optionally sets the default language environment variable based on credential data (defaults to Russian).
Troubleshooting
- Missing Credentials or Webhook URL: The node throws an error if no credentials or webhook URL are found. Ensure you have configured the Bitrix24 API credentials correctly.
- API Errors: If Bitrix24 returns an error (e.g., invalid field ID, insufficient permissions), the node surfaces the error description. Check that the field ID exists and your API token has proper rights.
- Invalid Enumeration Values: When updating enumeration fields, ensure the list values are properly formatted and non-empty; otherwise, the API may reject the request.
- Continue On Fail: If enabled, the node continues processing subsequent items even if one fails, returning error messages inline.