Bitrix24

Overview

This node integrates with the Bitrix24 CRM and business platform, allowing users to perform various operations on Bitrix24 resources. Specifically, for the Activity resource with the Delete operation, it enables deleting an activity by its ID from the Bitrix24 system.

Common scenarios where this node is beneficial include:

• Automating cleanup of outdated or irrelevant activities in Bitrix24.
• Integrating Bitrix24 activity management into broader workflows, such as removing completed tasks or calls automatically.
• Maintaining data hygiene by programmatically deleting activities based on external triggers or conditions.

Practical example:

• A workflow that deletes a specific activity after a related deal is closed or canceled, ensuring the CRM stays up-to-date without manual intervention.

Properties

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 an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.

No binary data output is involved in this operation.

Dependencies

• Requires authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
• Relies on Bitrix24's REST API endpoints to perform the delete action.
• The node uses internal helper functions to make standardized API calls to Bitrix24.

Troubleshooting

• Common issues:

  • Invalid or missing Activity ID: The node requires a valid activity ID; ensure this is correctly provided.
  • Authentication failures: Incorrect or expired credentials will prevent the node from connecting to Bitrix24.
  • Insufficient permissions: The authenticated user must have rights to delete activities in Bitrix24.

• Error messages:

  • Errors returned from Bitrix24 API will be included in the output JSON under the error field if "Continue On Fail" is enabled.
  • Common errors include "Activity not found" or "Access denied," indicating either a wrong ID or permission issues.

• Resolutions:

  • Verify the Activity ID exists in Bitrix24.
  • Check and refresh authentication credentials.
  • Confirm the user has appropriate permissions in Bitrix24 to delete activities.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 Activities Overview
• n8n Documentation on Creating Nodes