Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically allowing operations on calendar events such as deleting an event. The "Delete Event" operation under the "Calendar" resource enables users to remove a specific event from a user, group, or company calendar by specifying the event's ID and the calendar owner.

Common scenarios include:

  • Automating cleanup of outdated or canceled meetings.
  • Integrating Bitrix24 calendar management into broader workflows, e.g., removing events after a related CRM deal is closed.
  • Synchronizing external calendar systems by deleting events in Bitrix24 when they are removed elsewhere.

Example: Automatically delete a meeting event from a user's calendar when a corresponding task is marked complete in another system.

Properties

Name Meaning
Authentication Method to authenticate API calls:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key authentication
Type Type of calendar to operate on:
- User
- Group
- Company calendar
Owner ID Identifier of the calendar owner (user, group, or company)
Event ID Identifier of the calendar event to delete
Options Additional optional parameters:
- Access Token: Use a specific access token instead of credentials
- Filter: JSON filter criteria (not typically used for delete)
- Order: JSON sort order (not typically used for delete)

Output

The node outputs an array of items where each item contains a json object representing the result of the operation. For the "Delete Event" operation, the output typically includes confirmation of deletion or error details if the operation failed.

If an error occurs and the node is configured to continue on failure, the output will contain an error field with the error message, along with the resource name and a timestamp.

No binary data output is expected from this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
  • The node depends on Bitrix24's API endpoints for calendar management.
  • Proper permissions must be granted to the authenticated user or application to delete calendar events.
  • No additional environment variables are explicitly required beyond standard n8n credential setup.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect or missing Owner ID or Event ID causing the API to fail to locate the event.
    • Insufficient permissions to delete events on the specified calendar type.
    • Network connectivity issues preventing API calls.
  • Error messages:

    • Authorization errors: Check that the authentication method is correctly configured and tokens are valid.
    • "Event not found": Verify that the Event ID and Owner ID correspond to an existing event.
    • Permission denied: Ensure the authenticated user has rights to modify the specified calendar.
    • JSON parsing errors in options: Confirm that any JSON provided in filters or orders is well-formed.
  • Resolution tips:

    • Refresh or reauthenticate credentials if authorization fails.
    • Double-check input IDs for correctness.
    • Review Bitrix24 user roles and permissions.
    • Validate JSON inputs using online tools before entering them.

Links and References

Discussion