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 platform, specifically allowing interaction with various Bitrix24 resources such as CRM entities and timelines. The "Timeline" resource with the "Get Comment Fields" operation enables users to retrieve metadata about comment fields associated with timeline entries in Bitrix24.
Typical use cases include:
- Fetching available comment field definitions to dynamically build forms or filters.
- Automating workflows that depend on specific comment attributes within Bitrix24 timelines.
- Integrating Bitrix24 timeline comments into external systems by understanding their structure.
For example, a user might want to list all comment fields to allow selection of which fields to display or filter on in a custom dashboard.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Options | Additional parameters to customize the request: - Filter: JSON object specifying filter criteria - Order: JSON object specifying sort order - Start: Number indicating pagination start position |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 for the requested resource and operation.
For the "Get Comment Fields" operation under the "Timeline" resource, the output json will contain the metadata of comment fields retrieved from Bitrix24. This typically includes field IDs, labels, types, and other descriptive information about each comment field.
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).
- Uses Bitrix24 API endpoints internally to fetch resource data.
- No additional external services beyond Bitrix24 are required.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials. OAuth2 tokens may expire and require refresh.
- API call failures: Network issues or incorrect permissions in Bitrix24 can cause API calls to fail. Verify API access rights and network connectivity.
- Invalid filter/order JSON: If using the "Filter" or "Order" options, ensure the JSON syntax is correct and matches Bitrix24 API expectations.
- Empty or missing results: This may indicate no comment fields exist or insufficient permissions. Confirm that the Bitrix24 account has access to timeline comment data.
- Error messages in output: When
continueOnFailis enabled, errors are returned in the output JSON under anerrorproperty with a timestamp. Review these messages for troubleshooting.