Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 CRM and business resources. Specifically, for the Activity resource with the Delete operation, it enables deleting an existing activity by its ID. This is useful in scenarios where you want to automate cleanup or management of activities within Bitrix24, such as removing outdated tasks, calls, or events programmatically.

Practical examples include:

  • Automatically deleting completed or canceled activities from Bitrix24 to keep the CRM clean.
  • Integrating with other workflows that require removing specific activities based on external triggers or conditions.
  • Managing activity lifecycle in bulk via automation.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Activity ID The unique identifier of the activity to delete. This is required to specify which activity to remove.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs a JSON object containing:

  • error: The error message describing what went wrong.
  • resource: The resource name ("activity").
  • timestamp: The ISO timestamp when the error occurred.

No binary data output is involved in this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
  • The node depends on Bitrix24's REST API endpoints to perform operations.
  • Proper configuration of credentials in n8n is necessary to authorize API requests.

Troubleshooting

  • Common issues:

    • Invalid or missing Activity ID: Ensure the Activity ID provided exists and is correct.
    • Authentication failures: Verify that the selected authentication method is correctly configured and authorized.
    • API rate limits or permission errors from Bitrix24 may cause failures.
  • Error messages:

    • Errors returned from Bitrix24 API will be surfaced in the node’s output if "Continue On Fail" is enabled.
    • Common error messages might include "Activity not found" or "Access denied," indicating either the ID does not exist or insufficient permissions.
  • Resolution tips:

    • Double-check the Activity ID input.
    • Confirm that the API credentials have sufficient rights to delete activities.
    • Review Bitrix24 API documentation for any additional requirements or limitations.

Links and References

Discussion