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 such as contacts, deals, leads, companies, quotes, invoices, products, and activities. Specifically, for the Product resource and the Get Product Fields operation, it fetches metadata about the fields available in Bitrix24's product entity.
This is useful when you want to dynamically retrieve the list of fields that exist for products in your Bitrix24 instance, for example, to build dynamic forms, validate data before sending it to Bitrix24, or map fields between systems.
Practical examples:
- Automatically loading all available product fields to create a custom UI form for product data entry.
- Fetching field metadata to understand which fields are required or read-only before creating or updating products.
- Using the field list to configure other automation steps that depend on product attributes.
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 an array of objects representing the fields of the selected Bitrix24 resource (in this case, product fields). Each object typically contains:
name: The display label of the field (e.g., "Product Name").value: The internal field ID used by Bitrix24 (e.g., "NAME").description: Additional information about the field, such as its type and whether it is required.
The output JSON structure looks like this (example):
[
{
"name": "Product Name",
"value": "NAME",
"description": "string - Field ID: NAME"
},
{
"name": "Price",
"value": "PRICE",
"description": "double - Field ID: PRICE"
}
]
No binary data output is produced by this operation.
Dependencies
Requires connection to a Bitrix24 instance via one of the supported authentication methods:
- OAuth2 token credential
- Webhook URL
- API key credential
The node internally calls Bitrix24 API endpoints such as
crm.product.fieldsto retrieve field metadata.Proper configuration of credentials in n8n is necessary to authenticate API requests.
Troubleshooting
Common issues:
- Failure to load fields due to incorrect or expired authentication credentials.
- Network connectivity problems preventing API calls.
- Insufficient permissions in Bitrix24 user account to access product metadata.
Error messages:
"Failed to load CRM fields: <error message>"β Indicates an issue during the API call; check credentials and network."Error loading fields"β Generic error when fetching fields; inspect node execution logs for details.
Resolutions:
- Verify that the chosen authentication method is correctly configured and valid.
- Ensure the Bitrix24 user has permission to access product data.
- Check network connectivity and firewall settings.
- If using webhook authentication, confirm the webhook URL is correct and active.