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 interacts with the Bitrix24 platform, specifically focusing on retrieving user field types when the "User Field" resource and "Get User Field Types" operation are selected. It is designed to fetch metadata about custom or system fields defined in Bitrix24, which can be useful for dynamically understanding available fields in a Bitrix24 instance.
Common scenarios where this node is beneficial include:
- Automating workflows that depend on dynamic field configurations in Bitrix24.
- Integrating Bitrix24 user field metadata into other systems or reports.
- Preparing data mappings by fetching field definitions before processing records.
For example, a user might use this node to retrieve all user-defined fields for CRM contacts to build a form or synchronize these fields with another database.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key. |
| Options | Additional options collection. Contains: - Access Token: String token used for authentication if applicable. |
Output
The node outputs an array of items, each containing JSON data representing the result of the requested operation. For the "Get User Field Types" operation, the output JSON typically includes:
- Metadata about user fields such as field IDs, names, labels, types, and other configuration details.
- In case of errors, the output JSON contains an
errormessage, theresourcename, and atimestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- The node depends on internal helper functions to make API calls to Bitrix24 endpoints.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to Bitrix24 API endpoints is necessary.
Troubleshooting
- Authentication Errors: Ensure that the correct authentication method is selected and that valid credentials or tokens are provided.
- API Call Failures: Could be due to network issues, incorrect permissions, or invalid parameters. Check the error messages returned in the output JSON.
- Empty or Missing Fields: If no user fields are returned, verify that the Bitrix24 account has user fields defined and that the API user has sufficient permissions.
- Continue On Fail Behavior: If enabled, the node will output error information instead of failing the workflow outright, allowing graceful error handling.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 User Fields Overview
- n8n documentation on Bitrix24 Integration (for general usage)