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
The node integrates with the Bitrix24 CRM and business platform, allowing users to interact with various Bitrix24 resources such as contacts, deals, leads, companies, quotes, invoices, products, and activities. Specifically, for the Product resource and the Get Product Properties operation, the node fetches metadata about product fields available in the Bitrix24 CRM.
This is useful when you want to dynamically retrieve the list of product properties (fields) that can be used in other operations, such as creating or updating products, or for building dynamic UI elements based on available product data.
Practical examples:
- Automatically loading all available product fields to map data from an external system.
- Displaying product field options in a dropdown for user selection in subsequent workflow steps.
- Validating input data against the actual product fields defined in Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs JSON data representing the result of the requested operation on the selected resource. For the "Get Product Properties" operation, the output JSON contains an array of product field definitions, each including:
- Field ID (internal identifier)
- Field display name (label)
- Field type
- Whether the field is required
- Additional descriptive information
If an error occurs during the API call, the output JSON will contain an error property with the error message, the resource name, and a timestamp.
The node does not output binary data.
Dependencies
Requires connection to a Bitrix24 instance via one of the supported authentication methods:
- OAuth2 authentication token
- Webhook URL
- API key credential
The node uses Bitrix24's REST API endpoints to fetch CRM entity fields.
No additional external dependencies beyond standard n8n credentials and HTTP request capabilities.
Troubleshooting
Common issues:
- Incorrect or expired authentication credentials leading to authorization errors.
- Network connectivity problems preventing API calls.
- Bitrix24 API rate limits or temporary unavailability.
- Selecting an unsupported or misspelled resource or operation.
Error messages:
"Failed to load CRM fields: <message>": Indicates failure to retrieve fields from Bitrix24. Check API credentials and network access.- Generic API errors returned by Bitrix24 will be included in the
errorfield of the output JSON.
Resolution tips:
- Verify that the authentication method is correctly configured and valid.
- Ensure the Bitrix24 account has sufficient permissions to access CRM product fields.
- Retry after some time if encountering rate limits or transient API errors.
- Use the "continue on fail" option in the node settings to handle errors gracefully in workflows.