Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform to manage calendar events, specifically allowing users to set the meeting status of a calendar event. It is useful in scenarios where automated workflows need to update the participation status of meetings, such as accepting, declining, or tentatively responding to invitations programmatically.

Practical examples include:

  • Automatically marking a meeting as accepted when certain conditions are met.
  • Declining meetings based on availability or other business rules.
  • Setting tentative status for meetings pending confirmation.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Type Type of calendar to operate on: User, Group, or Company calendar.
Owner ID Identifier of the calendar owner whose event status will be updated.
Event ID Identifier of the specific calendar event to update.
Meeting Status The status to set for the meeting: Accepted, Declined, or Tentative.
Options Additional optional parameters:
- Access Token Override the default access token with a custom one.
- Filter JSON-formatted filter criteria (not typically used for this operation).
- Order JSON-formatted sort order (not typically used for this operation).

Output

The node outputs an array of items corresponding to the processed requests. Each item contains a json field with the response data from Bitrix24 after setting the meeting status. If an error occurs and "Continue On Fail" is enabled, the output includes an error object with the message, resource name, and timestamp.

If binary data were involved (not applicable here), it would be summarized accordingly.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
  • Proper credentials must be configured in n8n for the chosen authentication method.
  • Network access to Bitrix24 API endpoints is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect Owner ID or Event ID causing "not found" errors.
    • Insufficient permissions for the authenticated user to modify calendar events.

  • Error Messages:

    • Authorization failures: Check that the API key, OAuth2 token, or webhook URL is valid and has required scopes.
    • Resource not found: Verify that the provided calendar owner and event IDs exist and are correct.
    • API rate limits: If too many requests are made, Bitrix24 may throttle; implement retries or delays.

  • Resolutions:

    • Refresh or reconfigure credentials.
    • Double-check input IDs for correctness.
    • Ensure the authenticated user has appropriate rights in Bitrix24.
    • Use the "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion