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, allowing users to interact with various Bitrix24 resources programmatically. Specifically, for the Data Storage resource and the Get Entity Item Properties operation, it retrieves metadata about the properties (fields) of a specified entity item within Bitrix24.
Typical use cases include:
- Dynamically fetching available fields of CRM entities such as contacts, deals, leads, companies, quotes, invoices, or custom Smart Process Automation (SPA) entities.
- Using the retrieved field information to build dynamic forms or automate workflows that depend on entity structure.
- Validating or mapping data before creating or updating records in Bitrix24 by knowing which fields are available and their characteristics.
For example, a user might want to get all the fields of a "Deal" entity to understand what data can be set or extracted when automating sales processes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Note: The provided input properties JSON only includes the Authentication property, but the node internally supports selecting Resource and Operation as well.
Output
The output is an array of objects representing the properties (fields) of the selected entity item. Each object typically contains:
name: The display name or label of the field.value: The internal field identifier used in Bitrix24 API calls.description: A string describing the field type and whether it is required or read-only.
The fields are sorted by a custom order prioritizing common important fields (like TITLE, OPPORTUNITY, ASSIGNED_BY_ID) and then alphabetically.
If the node encounters an error while fetching fields, the output will contain an error message inside the json property.
The node does not output binary data.
Example output snippet (conceptual):
[
{
"name": "Title",
"value": "TITLE",
"description": "string (Required)"
},
{
"name": "Opportunity",
"value": "OPPORTUNITY",
"description": "double"
},
{
"name": "Assigned By",
"value": "ASSIGNED_BY_ID",
"description": "user ID"
}
]
Dependencies
- Requires connection to Bitrix24 API via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Uses internal helper functions to make standard Bitrix24 API calls.
- No additional external services beyond Bitrix24 itself.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
Common issues:
- Incorrect or expired authentication credentials leading to authorization errors.
- Selecting an unsupported or invalid entity type/resource may result in empty or error responses.
- Network connectivity problems preventing API calls.
Error messages:
"Failed to load CRM fields: <error message>"indicates an issue retrieving fields from Bitrix24; check API permissions and network."No fields available"means the selected entity has no retrievable fields or the API returned no data.- If the node returns an error in the output JSON with a timestamp, it means the node was configured to continue on failure and caught an exception during execution.
Resolution tips:
- Verify authentication credentials and refresh tokens if using OAuth2.
- Confirm the entity type parameter is correctly set.
- Check Bitrix24 API limits and permissions.
- Enable detailed logging in n8n to inspect API call responses.