Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, for the Activity - Get operation, it retrieves detailed information about a specific activity within Bitrix24 by its unique ID. This is useful in scenarios where you want to fetch data about calls, meetings, tasks, or other tracked activities related to your CRM records.
Practical examples include:
- Fetching details of a scheduled call or meeting to display or process further.
- Retrieving an activity's status or notes before updating or reporting.
- Integrating activity data into workflows for notifications or analytics.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Activity ID | The unique identifier of the activity to retrieve. Required for this operation. |
Output
The node outputs JSON data representing the full details of the requested activity from Bitrix24. This includes all standard and custom fields associated with that activity, such as creation date, modification date, responsible user IDs, and any other metadata Bitrix24 provides for activities.
If the node supports binary data output (not explicitly shown here), it would typically represent attachments or files related to the activity, but this is not indicated in the provided code.
Dependencies
Requires valid authentication credentials configured in n8n for Bitrix24, which can be one of:
- OAuth2 token
- Webhook URL
- API key
Uses Bitrix24 API endpoints internally via a generic resource handler factory to perform the actual API calls.
No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials will cause API call failures.
- Providing an incorrect or non-existent Activity ID will result in errors or empty responses.
- Network connectivity problems may prevent successful API communication.
Error messages:
- Errors thrown during execution will include the error message from Bitrix24 API or network layer.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with an
errorfield containing the message.
Resolutions:
- Verify and refresh authentication credentials.
- Double-check the Activity ID for correctness.
- Ensure stable internet connection and Bitrix24 service availability.