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, the "Activity" resource with the "Get Fields" operation enables users to dynamically retrieve metadata about the fields available for activities in Bitrix24.
This is useful when building workflows that need to adapt to the structure of Bitrix24 data dynamically, for example:
- Automatically generating forms or UI elements based on available activity fields.
- Validating or mapping incoming data against the current Bitrix24 activity schema.
- Synchronizing or exporting activity data with external systems by understanding field definitions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating 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 available for the selected Bitrix24 resource (in this case, Activity). Each object typically contains:
name: The display label of the field (e.g., "Subject", "Start Date").value: The internal field ID used in Bitrix24 API calls.description: Additional information about the field, such as its type and whether it is required.
If an error occurs during fetching, the output will contain an object with an error message describing the failure.
The output is structured as JSON data under the json property of each item. This node does not output binary data.
Dependencies
Requires a valid Bitrix24 authentication credential configured in n8n, which can be one of:
- OAuth2 token
- Webhook URL
- API key
Uses Bitrix24 REST API endpoints to fetch field metadata.
No additional external dependencies beyond standard HTTP requests to Bitrix24 API.
Troubleshooting
Common Issues:
- Incorrect or expired authentication credentials may cause API call failures.
- Network connectivity issues can prevent successful communication with Bitrix24.
- Selecting an unsupported or invalid resource/entity type may result in empty or error responses.
Error Messages:
"Failed to load CRM fields: <error message>"indicates a problem retrieving fields from Bitrix24. Verify authentication and API permissions."Error loading fields"or similar messages suggest issues in the API response or internal processing errors.
Resolutions:
- Ensure the chosen authentication method is correctly set up and authorized.
- Check network access to Bitrix24 endpoints.
- Confirm the resource and entity types are valid and supported by your Bitrix24 instance.