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
This node integrates with the Bitrix24 platform, specifically allowing users to interact with Bitrix24 tasks. The Get Task operation retrieves detailed information about a specific task by its ID. This is useful in scenarios where you want to fetch task details for reporting, automation workflows, or synchronization with other systems.
Practical examples include:
- Fetching task details to display in a dashboard.
- Retrieving task status and metadata before updating or commenting on it.
- Automating notifications based on task properties.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Task ID | The unique identifier of the task to retrieve. |
| Options | Additional optional parameters as JSON objects: - Filter: Criteria to filter tasks (JSON format). - Order: Sorting order (JSON format). - Select: Specific fields to select (JSON array). - Group: Grouping criteria (JSON format). - Custom Parameters: Any extra parameters (JSON format). - Access Token: Optional access token string for authentication. |
Output
The node outputs an array of items, each containing a json object representing the retrieved task data from Bitrix24. The structure of this JSON corresponds to the task's properties as returned by the Bitrix24 API, including fields such as task ID, title, description, status, assigned users, deadlines, and other metadata.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use).
- Webhook URL authentication (simpler but less secure).
- API key authentication.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to the Bitrix24 API endpoints.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Task ID causing "task not found" or empty results.
- Malformed JSON in options like filter, order, or select causing API request failures.
- Network connectivity problems preventing API calls.
Error messages:
- Errors thrown by the node typically include the message from the Bitrix24 API or internal processing errors.
- If "Continue On Fail" is enabled, errors are returned in the output JSON under the
errorproperty.
Resolutions:
- Verify that the authentication credentials are valid and have sufficient permissions.
- Double-check the Task ID for correctness.
- Ensure JSON inputs in options are well-formed.
- Check network connectivity and firewall settings.