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, the Activity - Update operation enables updating details of an existing activity within Bitrix24, such as calls, emails, meetings, or tasks.
This node is beneficial in scenarios where you want to programmatically modify activities based on workflow triggers or external events. For example:
- Automatically updating the subject or timing of a scheduled call after receiving new information.
- Changing the responsible user for a task when team assignments change.
- Adjusting meeting times dynamically based on calendar availability.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Activity ID | The unique identifier of the activity to update. |
| Update Fields | Collection of fields to update on the activity: |
| - Subject | New subject/title of the activity. |
| - Type | Type of activity; options are Call, Email, Meeting, or Task. |
| - Responsible ID | ID of the user responsible for the activity. |
| - Start Time | New start time of the activity (date-time). |
| - End Time | New end time of the activity (date-time). |
Output
The node outputs an array of JSON objects representing the updated activity data returned from Bitrix24. Each item corresponds to one processed input and contains the updated fields as confirmed by the Bitrix24 API response.
If an error occurs and "Continue On Fail" is enabled, the output will include an object with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is produced by this node.
Dependencies
Requires authentication credentials for Bitrix24 via one of these methods:
- OAuth2 token
- Webhook URL
- API key
The node depends on Bitrix24's REST API endpoints for CRM activities.
Proper configuration of credentials in n8n is necessary before use.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Providing an incorrect or non-existent Activity ID causing "not found" errors.
- Missing required fields in the update payload resulting in validation errors.
- Date/time format errors if Start Time or End Time are not properly formatted.
Error messages:
- Authorization failures: Check that the selected authentication method is correctly configured and valid.
- Activity not found: Verify the Activity ID exists in Bitrix24.
- Validation errors: Ensure all required update fields meet Bitrix24 API requirements.
- Network or API errors: Confirm network connectivity and Bitrix24 service status.
Enabling "Continue On Fail" can help workflows proceed despite individual errors, allowing error handling downstream.