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 perform various operations on Bitrix24 resources. Specifically, for the Activity resource with the Get operation, it retrieves detailed information about a specific activity by its ID.
Common scenarios where this node is beneficial include:
- Fetching details of a particular CRM activity (e.g., calls, meetings, tasks) to use in workflows.
- Automating follow-up actions based on activity data.
- Integrating Bitrix24 activity data into other systems or reports.
Practical example:
- A workflow that triggers when a new activity is created and then uses this node to get full details of that activity for further processing or notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Activity ID | The unique identifier of the activity to retrieve. This is required for the Get operation on the Activity resource. |
Output
The node outputs JSON data representing the retrieved activity's details from Bitrix24. The structure typically includes all fields related to the activity such as IDs, timestamps, user references, and custom fields defined in Bitrix24.
If the node supports binary data output (not explicitly shown here), it would represent any associated files or attachments linked to the activity.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's REST API endpoints to fetch activity data.
- Proper configuration of authentication credentials in n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Providing an incorrect or non-existent Activity ID causing "not found" errors.
- Network connectivity problems preventing API communication.
Error messages and resolutions:
"error": "Invalid credentials": Check and update your authentication method and credentials."error": "Activity not found": Verify the Activity ID is correct and exists in Bitrix24.- Timeout or network errors: Ensure stable internet connection and Bitrix24 API availability.
Enabling "Continue On Fail" allows the workflow to proceed even if this node encounters errors, returning error details in the output JSON.