Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The Bitrix24 node integrates with the Bitrix24 CRM and business platform, allowing users to interact with various resources such as calendars, CRM entities, and more. Specifically, for the Calendar resource and the Get Meeting Status operation, this node retrieves the status of a meeting event from a specified calendar.

This operation is useful in scenarios where you need to programmatically check the current status of a meeting (e.g., confirmed, cancelled, pending) within a Bitrix24 calendar. For example, automating workflows that depend on meeting statuses, such as sending reminders only for confirmed meetings or updating CRM records based on meeting outcomes.

Properties

Name Meaning
Authentication Method of authentication to use:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key
Type Type of calendar to query:
- User
- Group
- Company calendar
Owner ID The identifier of the calendar owner whose calendar is being accessed
Event ID The identifier of the specific calendar event (meeting) to get the status for
Options Additional optional parameters:
- Access Token: Use a specific access token instead of credentials
- Filter: JSON object to filter results
- Order: JSON object to specify sort order

Output

The output contains a JSON object representing the meeting status information retrieved from the Bitrix24 calendar event. This typically includes details about the event's current state, such as whether it is confirmed, tentative, or cancelled, along with any other metadata returned by the Bitrix24 API related to the meeting status.

If the node encounters an error and "Continue On Fail" is enabled, the output will include an error object with the error message, the resource name, and a timestamp.

The node does not output binary data for this operation.

Dependencies

  • Requires connection to a Bitrix24 instance.
  • Requires one of the following authentication methods configured in n8n:
    • OAuth2 authentication (recommended)
    • Webhook URL authentication
    • API key authentication
  • The node uses Bitrix24 API endpoints internally to fetch calendar and event data.
  • No additional external dependencies beyond Bitrix24 API access.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens can cause authorization failures.
    • Incorrect Owner ID or Event ID values may result in "not found" errors.
    • Insufficient permissions for the authenticated user to access the specified calendar or event.
    • Malformed JSON in the Filter or Order options can cause request errors.

  • Error Messages:

    • Errors thrown by the Bitrix24 API are surfaced in the node output if "Continue On Fail" is enabled.
    • Typical error messages include authentication failures, missing required parameters, or API rate limits.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Double-check the correctness of Owner ID and Event ID.
    • Ensure the authenticated user has appropriate permissions.
    • Validate JSON syntax in optional filter/order fields.

Links and References

Discussion