Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The node integrates with the Bitrix24 platform, specifically allowing interaction with its Calendar resource. The "Update Section" operation updates an existing calendar section by specifying its ID and providing new data for that section in JSON format. This is useful for automating calendar management tasks such as renaming sections, changing colors, or modifying access permissions programmatically.

Practical examples include:

  • Automatically updating calendar sections based on external triggers or workflows.
  • Synchronizing calendar section details from other systems.
  • Managing calendar organization dynamically within business automation processes.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
Section ID The unique identifier of the calendar section to update.
Section Data JSON object containing the updated data for the calendar section (e.g., name, color, permissions).
Options Additional optional parameters:
- Access Token: Override the 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 updating the calendar section. The exact structure depends on Bitrix24's API response but typically includes confirmation of the update and the updated section details.

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

No binary data output is involved in this operation.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
  • Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
  • Relies on Bitrix24's API endpoint for calendar section updates.

Troubleshooting

  • Common issues:
    • Invalid or missing Section ID will cause the update to fail.
    • Malformed JSON in Section Data can lead to API errors.
    • Insufficient permissions or incorrect authentication may result in authorization errors.
  • Error messages:
    • Errors returned from Bitrix24 API are passed through; typical messages include invalid token, not found, or validation errors.
    • If "Continue On Fail" is enabled, errors are returned in the output JSON with an error message and timestamp for easier debugging.
  • Resolution tips:
    • Verify the Section ID exists and is correct.
    • Ensure the JSON in Section Data is valid and matches expected schema.
    • Confirm authentication credentials are correctly set up and have necessary permissions.

Links and References

Discussion