Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This node integrates with the Bitrix24 CRM and business platform, specifically allowing users to add multiple custom user fields to various entity types within Bitrix24. The "Add Multiple" operation under the "User Field Config" resource enables batch creation of custom fields for entities such as Deals, Leads, Contacts, Companies, Quotes, Smart Processes, or custom-defined entities.
Common scenarios include:
- Automating the setup of multiple custom fields in Bitrix24 entities to tailor the CRM data structure to specific business needs.
- Bulk configuration of fields when onboarding new processes or migrating data.
- Managing complex field setups programmatically rather than manually through the Bitrix24 UI.
Practical example:
A sales team wants to add several custom fields (e.g., "Customer Priority", "Contract Signed Date", "Renewal Probability") to the Deal entity to better track deal progress. Using this node, they can define all these fields at once and apply them automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Use Structure Builder | Whether to use a UI builder for defining field configurations or input raw JSON directly. |
| Entity Type | The type of entity to which the fields will be added. Options: Deal, Lead, Contact, Company, Quote, Smart Process, or Custom. |
| Custom Entity Type | If "Custom" is selected as Entity Type, specify the custom entity type string here. |
| Smart Process Type | If "Smart Process" is selected as Entity Type, select the specific Smart Process type. This ID is used in the field naming convention. |
| Field Definitions | A collection of multiple field definitions to create. Each field includes: • Field Type (string, integer, double, boolean, date, datetime, enumeration, file, employee, money, url, address, resource booking, crm entity, crm status, crm category, html) • Field Name (Latin letters, numbers, underscores; prefix added automatically) • Label (user-friendly name) • Multiple Values (boolean) • Mandatory (boolean) • Filterable (boolean) • Searchable (boolean) • Default Value (string) • Additional Settings (JSON object for extra configuration) |
| Options - Access Token | Access token string for authentication (if applicable). |
Output
The node outputs an array of items corresponding to the result of processing the requested operation. Each item contains a json property with the response from Bitrix24 after attempting to add the specified user fields.
- The output JSON typically includes success confirmation or error details per field created.
- No binary data output is indicated by the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Needs proper API credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to create and configure user fields.
- Uses internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
- Authentication errors: Ensure that the provided access token or webhook URL is valid and has sufficient permissions to modify user fields.
- Invalid field names: Field names must contain only Latin letters, numbers, and underscores. The node automatically adds required prefixes, but invalid characters may cause API errors.
- Missing required parameters: For Smart Process entity types, selecting the correct Smart Process type is mandatory.
- API rate limits or connectivity issues: Network problems or Bitrix24 API limits might cause failures; retry or check API usage quotas.
- Malformed additional settings JSON: If the "Additional Settings" JSON is invalid, the API call may fail. Validate JSON syntax before execution.
- Error messages: The node returns error messages in the output JSON under the
errorkey if the operation fails and "Continue On Fail" is enabled.