Actions20
Overview
This node allows you to manage custom user fields in Bitrix24 CRM entities, specifically for the "Deal" resource when creating a new custom field. It enables adding tailored fields to deals to capture additional information not covered by default fields. This is useful for businesses that need to track specialized data points related to deals, such as custom statuses, categories, or financial details.
Typical use cases include:
- Adding a custom dropdown list of deal types.
- Creating a mandatory numeric field for internal scoring.
- Defining date or datetime fields for tracking deadlines or milestones.
By automating the creation of these fields, users can streamline their CRM customization directly from n8n workflows without manual configuration in Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Field Name | The internal identifier of the custom field (e.g., UF_CRM_CUSTOM_FIELD). Required. |
| Field Label | The display name shown in the Bitrix24 UI for this field. Required. |
| Field Type | The data type of the custom field. Options: String, Integer, Double, Boolean, Enumeration (list), Date, Datetime, File, Money, URL. Required. |
| List Values | For "Enumeration" type only: defines the selectable values in the dropdown list. Multiple values can be added and sorted. |
| Multiple | Whether the field supports multiple values (true/false). |
| Mandatory | Whether the field is required (true/false). |
| Show Filter | Whether to show this field in filters (true/false). |
| Show In List | Whether to show this field in lists (true/false). |
Output
The node outputs an array of JSON objects representing the API response(s) from Bitrix24 after attempting the create operation. Each object contains the result of the user field creation request, including success status and any returned IDs or error messages.
No binary data output is produced by this node.
Example output JSON structure (simplified):
[
{
"result": {
"ID": "123",
"FIELD_NAME": "UF_CRM_CUSTOM_FIELD"
}
}
]
Dependencies
- Requires an active Bitrix24 account with API access.
- Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- Uses the Bitrix24 webhook URL to send requests.
- Relies on the axios HTTP client library for making API calls.
Troubleshooting
- Missing Credentials: If no credentials or webhook URL are provided, the node will throw an error indicating missing authentication details.
- API Errors: Bitrix24 API errors return descriptive messages; common issues include invalid field names, duplicate field identifiers, or insufficient permissions.
- Field Name Format: The field name must follow Bitrix24 conventions (usually starting with "UF_"). Using incorrect formats may cause API rejection.
- List Values for Enumeration: When using the enumeration type, ensure at least one list value is provided; otherwise, the API call may fail.
- Boolean Flags: The node converts boolean properties to "Y"/"N" strings as required by Bitrix24 API; setting these incorrectly might cause unexpected behavior.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output.