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 integrates with the Bitrix24 CRM and business platform, allowing users to interact programmatically with various Bitrix24 resources. Specifically, for the Task resource with the Start operation, this node enables initiating or starting tasks within Bitrix24.
This node is beneficial in automation workflows where task management needs to be integrated with other systems or processes. For example, automatically creating and starting a task when a new lead is added, or triggering task workflows based on external events.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Options | Collection of optional parameters to customize the request: - Filter: JSON object to filter tasks - Order: JSON object to specify sorting order - Select: JSON array specifying which fields to select - Group: JSON object defining grouping criteria - Custom Parameters: Additional JSON parameters to include - Access Token: String token for authentication override |
Output
The node outputs an array of items, each containing a json property with the response data from Bitrix24 related to the Task start operation. The exact structure depends on the Bitrix24 API response but typically includes details about the started task(s).
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.
No binary data output is indicated by the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, Webhook URL, or API Key).
- Uses internal helper functions to make standard Bitrix24 API calls.
- No additional external dependencies beyond Bitrix24 API access.
- Proper configuration of credentials in n8n is necessary for successful API communication.
Troubleshooting
Common Issues:
- Incorrect or expired authentication tokens leading to authorization errors.
- Malformed JSON in options such as Filter, Order, Select, Group, or Custom Parameters causing API call failures.
- Network connectivity issues preventing access to Bitrix24 API endpoints.
Error Messages:
- Errors thrown during execution will include the message from the underlying API or network failure.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with fields
error,resource, andtimestamp.
Resolutions:
- Verify and refresh authentication credentials.
- Validate JSON syntax in all input properties before running the node.
- Ensure network access to Bitrix24 services.
- Enable "Continue On Fail" to handle errors gracefully in workflows.