Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform to update calendar events. It allows users to modify existing events in a specified calendar owned by a user, group, or company. This is useful for automating calendar management tasks such as rescheduling meetings, updating event details, or correcting event information without manual intervention.

Practical examples include:

  • Automatically updating meeting times based on CRM workflow triggers.
  • Changing event descriptions or attendees when related data changes in Bitrix24.
  • Synchronizing external calendar updates into Bitrix24 calendars programmatically.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key
Type Type of calendar to update: User, Group, or Company calendar
Owner ID Identifier of the calendar owner whose event is being updated
Event ID Identifier of the specific calendar event to update
Event Data JSON object containing the new data for the event
Options Additional optional parameters:
- Access Token: override default token
- Filter: JSON filter criteria
- Order: JSON sort order

Output

The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to update the event. The exact structure depends on Bitrix24's API response but typically includes confirmation of the update and possibly the updated event details.

If an error occurs and "Continue On Fail" is enabled, the output will contain an error message with the resource name and timestamp.

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 for calendar event management.
  • No additional external libraries beyond those bundled are required.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens causing authorization failures.
    • Incorrect Owner ID or Event ID leading to "event not found" errors.
    • Malformed JSON in Event Data causing request rejection.
    • Insufficient permissions for the authenticated user to update the specified calendar.

  • Error messages:

    • Errors returned from Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
    • Typical errors include authentication failures, invalid IDs, or validation errors on event data.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Double-check that Owner ID and Event ID correspond to existing entities.
    • Validate JSON syntax and required fields in Event Data.
    • Ensure the authenticated user has appropriate access rights in Bitrix24.

Links and References

Discussion