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 allowing users to interact with various Bitrix24 resources such as CRM entities and business processes. The "Task" resource with the "Get" operation enables retrieving detailed information about a specific task by its ID.
Common scenarios for this node include:
- Fetching details of a particular task in Bitrix24 to use in workflows or automation.
- Integrating task data into other systems or reports.
- Triggering subsequent actions based on task properties or status.
Practical example:
- A workflow that retrieves a task's details when triggered, then updates another system with the task's status or assigned user.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Task ID | The unique identifier of the task to retrieve. This is required. |
| Options | Additional optional parameters to customize the request: |
| - Filter | JSON object specifying filter criteria to narrow down results (if applicable). |
| - Order | JSON object defining sort order of results. |
| - Select | JSON array listing specific fields to select in the response. |
| - Group | JSON object defining grouping criteria. |
| - Custom Parameters | JSON object for any additional custom parameters supported by the Bitrix24 API. |
Output
The node outputs an array of items where each item contains a json property holding the retrieved task data from Bitrix24. The structure of the json output corresponds to the task entity fields returned by the Bitrix24 API, including standard task attributes such as ID, title, description, status, assigned user, creation date, etc.
If an error occurs during execution and the node is configured to continue on failure, 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 valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's REST API endpoints to fetch task data.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect or missing Task ID causing the API call to fail or return no data.
- Malformed JSON in optional parameters (Filter, Order, Select, Group, Custom Parameters) causing request errors.
- Network connectivity issues preventing access to Bitrix24 API.
Error messages:
- Errors thrown by the node will 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
errorkey.
Resolutions:
- Verify and refresh authentication credentials.
- Ensure the Task ID is correct and exists in Bitrix24.
- Validate JSON syntax in optional parameters before running the node.
- Check network connectivity and firewall settings.