Actions20
Overview
This node manages custom user fields in Bitrix24 CRM entities such as Leads, Deals, Contacts, and Companies. It supports creating, updating, retrieving (single or all), and deleting user-defined fields for these resources. This is useful when you want to extend the default CRM data model with additional custom fields tailored to your business needs.
Typical use cases include:
- Adding new custom fields to capture extra information about leads or deals.
- Updating labels or properties of existing custom fields.
- Fetching details of a specific custom field or listing all custom fields for a resource.
- Removing obsolete or unused custom fields from the CRM.
For example, you might create a custom enumeration field on a Lead to track a lead source category, update its label later, or delete it if no longer needed.
Properties
| Name | Meaning |
|---|---|
| Field ID | The identifier of the custom user field (required for update, get, and delete operations) |
The node also supports other properties for different operations (not requested here), such as Field Name, Field Label, Field Type, List Values, Multiple, Mandatory, Show Filter, and Show In List.
Output
The node outputs JSON data representing the response from the Bitrix24 API for the performed operation:
- For Delete operation, the output JSON contains the result of the deletion request, typically indicating success or failure.
- For other operations (create, update, get, getAll), the output includes detailed information about the user fields as returned by Bitrix24.
No binary data output is produced by this node.
Dependencies
- Requires an active Bitrix24 API authentication credential configured in n8n.
- Uses the Bitrix24 webhook URL from credentials to send API requests.
- Relies on the
axiosHTTP client library for making POST requests to Bitrix24 REST endpoints.
Troubleshooting
- Missing Credentials or Webhook URL: The node throws errors if the Bitrix24 API credentials or webhook URL are not provided. Ensure credentials are correctly set up.
- API Errors: If Bitrix24 returns an error (e.g., invalid field ID, permission issues), the node surfaces the error message prefixed with "Bitrix24 API error:". Check the error description for guidance.
- Field ID Required: For delete operations, the "Field ID" property must be specified; otherwise, the node will fail.
- Continue On Fail: If enabled, the node captures individual item errors and continues processing others, returning error messages in the output JSON.