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 platform, specifically enabling interaction with its CRM and business process management features. The "Workflow" resource with the "Get Tasks" operation allows users to retrieve tasks related to workflows or business processes from Bitrix24.
Common scenarios for this node include:
- Automating task retrieval for monitoring workflow progress.
- Integrating Bitrix24 task data into other systems or dashboards.
- Filtering and sorting tasks based on custom criteria to streamline business process management.
For example, a user might configure this node to fetch all active tasks assigned to a particular department or user, sorted by due date, to generate daily reports or trigger notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Return All | Boolean flag indicating whether to return all available results or only a subset. When false, limits the number of pages loaded. |
| Max Pages to Load | Maximum number of pages to load when Return All is false. Each page contains up to 50 items. This limits how many paginated results are fetched. |
| Options | Collection of additional parameters: - Filter: JSON object specifying filter criteria for tasks. - Order: JSON object specifying sort order. - Start: Number indicating the record offset to start selection. - Access Token: String token for authentication override. |
Output
The node outputs an array of items where each item contains a json field representing a task retrieved from Bitrix24 workflows. The structure of each task's JSON depends on the Bitrix24 API response but typically includes fields such as task ID, status, assigned user, creation/modification dates, and other task metadata.
If the node supports binary data output (not explicitly shown in the provided code), it would represent attachments or files related to tasks; however, this is not indicated here.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions to read workflow tasks.
- Needs one of the supported authentication methods configured in n8n:
- OAuth2 credentials
- Webhook URL
- API key credential
- Uses Bitrix24 API endpoints internally via helper functions to fetch data.
- No additional external dependencies beyond standard HTTP requests to Bitrix24 APIs.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens. OAuth2 requires proper token refresh handling.
- API rate limits: Bitrix24 may limit the number of API calls; using pagination wisely and limiting
Max Pages to Loadcan help avoid hitting these limits. - Invalid filter/order JSON: The
FilterandOrderproperties expect valid JSON objects. Malformed JSON will cause errors. Validate JSON syntax before input. - Empty results: If no tasks are returned, verify that the filter criteria match existing tasks and that the user has permission to view them.
- Continue on Fail: If enabled, the node returns error details in the output instead of failing the workflow, which helps in debugging.