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
The Bitrix24 node integrates with the Bitrix24 CRM and business platform, allowing users to interact programmatically with various Bitrix24 resources. Specifically, the Task - Start operation initiates or starts a task-related process within Bitrix24. This can be useful for automating task creation, management, or triggering workflows based on tasks in Bitrix24.
Common scenarios include:
- Automatically starting tasks when certain conditions are met in other systems.
- Integrating task management into broader automation workflows.
- Filtering and sorting tasks dynamically before starting them.
Example use case:
- A sales team uses Bitrix24 for task tracking. When a new lead is qualified, an automated workflow triggers this node to start a related task with specific filters and parameters applied.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Options | Collection of optional JSON parameters to customize the task start operation: |
| Filter | JSON object defining criteria to filter which tasks to start. |
| Order | JSON object specifying the sort order of tasks. |
| Select | JSON array listing fields to select from the tasks. |
| Group | JSON object defining grouping criteria for tasks. |
| Custom Parameters | Additional custom parameters in JSON format to pass to the API call. |
Output
The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after attempting to start the task(s). The structure typically includes:
- Task details as returned by Bitrix24.
- In case of failure (if "Continue On Fail" is enabled), an error object with:
error: Error message string.resource: The resource name ("task").timestamp: ISO timestamp of the error occurrence.
No binary data output is indicated.
Dependencies
- Requires valid Bitrix24 credentials configured in n8n, supporting one of:
- OAuth2 authentication (recommended).
- Webhook URL authentication.
- API key authentication.
- Uses Bitrix24 API endpoints internally via a generic resource handler factory.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials. OAuth2 tokens may expire and need refreshing.
- Invalid JSON in options: The
filter,order,select,group, andcustomParametersfields expect valid JSON. Malformed JSON will cause errors. - API rate limits or connectivity issues: Bitrix24 API may throttle requests or be temporarily unavailable.
- Error messages: If the node throws an error, it will include the Bitrix24 API error message. Enabling "Continue On Fail" allows workflow continuation with error details in output.
- Missing required parameters: Although not explicitly shown, some Bitrix24 API calls require mandatory fields; ensure all necessary parameters are provided.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Tasks REST API
- n8n documentation on Bitrix24 integration
This summary is based solely on static analysis of the provided source code and input properties definition.