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 allows users to interact with the Bitrix24 CRM and business platform. Specifically, for the Task - Update operation, it updates an existing task in Bitrix24 by modifying its fields such as title, description, responsible user, deadline, priority, status, and other metadata.
This node is beneficial when automating task management workflows within Bitrix24, such as updating task details based on external triggers or integrating task updates from other systems. For example, you could automatically update a task's status to "Completed" when a related deal is closed, or change the responsible user based on workload distribution.
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 update. This is required. |
| Fields | Collection of fields to update on the task. Options include: • Title: Title of the task • Description: Detailed description • Responsible User ID: User assigned to the task • Deadline: Task deadline date/time • Priority: Low, Normal, High • Status: New, Pending, In Progress, Supposedly Completed, Completed, Deferred, Declined • Group ID: Group associated with the task • Created By: User who created the task • Start Date: Planned start date/time • End Date: Planned end date/time |
| Options | Additional optional parameters as JSON: • Filter: Filter criteria • Order: Sort order • Select: Fields to select • Group: Grouping criteria • Custom Parameters: Extra parameters • Access Token: Token for authentication |
Output
- The output is an array containing one item per input item.
- Each output item contains a
jsonobject representing the response from Bitrix24 after updating the task. - The exact structure depends on the Bitrix24 API response but typically includes updated task details.
- No binary data output is indicated.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs proper credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to perform task updates.
- The node uses internal helper functions and resource handlers to abstract API calls.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the update to fail.
- Incorrect authentication credentials or expired tokens can lead to authorization errors.
- Providing invalid field values (e.g., wrong date format or invalid user IDs) may cause API errors.
- Network connectivity problems can prevent communication with Bitrix24.
Error messages:
- Authorization errors: Check that the API key, OAuth token, or webhook URL is valid and has sufficient permissions.
- Validation errors: Verify that all required fields are correctly formatted and valid according to Bitrix24 API documentation.
- Rate limiting or API quota exceeded: Wait and retry later or check Bitrix24 account limits.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow workflow execution to proceed even if some updates fail.