Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to update an existing Activity record within Bitrix24 CRM. Activities in Bitrix24 represent tasks such as calls, emails, meetings, or tasks assigned to users.

Typical use cases include:

  • Updating the subject or type of a scheduled call or meeting.
  • Changing the responsible user for an activity.
  • Adjusting the start and end times of an activity to reflect rescheduling.

For example, after receiving updated scheduling information from another system, this node can be used to update the corresponding activity in Bitrix24 automatically.

Properties

Name Meaning
Authentication Method 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, Task
- Responsible ID User ID of the person 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 items where each item contains a json object representing the response from Bitrix24 after updating the activity. This typically includes the updated activity data or confirmation of the update operation.

If an error occurs and "Continue On Fail" is enabled, the output will contain an item 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 valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
  • The node relies on Bitrix24's REST API endpoints to perform the update operation.
  • Proper permissions in Bitrix24 are necessary to update activities.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials leading to authorization errors.
    • Providing an incorrect or non-existent Activity ID results in not found errors.
    • Missing required fields or invalid date formats in update fields may cause request failures.
  • Error messages:

    • Errors returned from Bitrix24 API will be surfaced in the node’s output if "Continue On Fail" is enabled.
    • Typical error messages include authentication failures, permission denied, or invalid parameters.
  • Resolution tips:

    • Verify that the authentication method and credentials are correctly configured.
    • Ensure the Activity ID exists and is accessible by the authenticated user.
    • Validate all input fields, especially date-time formats, before running the node.

Links and References

Discussion