Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to interact with various Bitrix24 resources such as CRM entities and timelines. The "Timeline" resource's "Delete Log Message" operation enables users to delete a specific log message from the Bitrix24 timeline by providing its ID.

Common scenarios for this node include automating cleanup of timeline entries, managing audit logs, or removing outdated or incorrect log messages programmatically within workflows. For example, after processing a certain event, a user might want to delete related timeline log messages to keep the timeline clean or comply with data retention policies.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key.
Log Message ID The unique identifier of the log message to be deleted from the timeline.
Options - Filter JSON object specifying filter criteria (not directly relevant for delete but available for other ops).
Options - Order JSON object specifying sort order (not directly relevant for delete but available for other ops).
Options - Start Number indicating start position for pagination (not directly relevant for delete but available for other ops).

Note: For the "Delete Log Message" operation on the "Timeline" resource, only the "Authentication" and "Log Message ID" properties are required and directly used.

Output

The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to delete the specified log message.

  • On success, the output typically includes confirmation details from Bitrix24 about the deletion.
  • On failure (if "Continue On Fail" is enabled), the output will contain an error object with:
    • error: The error message string.
    • resource: The resource name ("timeline").
    • timestamp: ISO timestamp of when the error occurred.

The node does not output binary data.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods:

    • OAuth2 token
    • Webhook URL
    • API key
  • The node depends on Bitrix24's REST API endpoints to perform operations.

  • No additional external services or environment variables are required beyond proper Bitrix24 credentials configured in n8n.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials leading to authorization errors.
    • Providing an incorrect or non-existent Log Message ID causing "not found" errors.
    • Network connectivity issues preventing API calls to Bitrix24.
  • Error Messages:

    • "error": "Invalid credentials": Check and refresh your authentication method.
    • "error": "Log message not found": Verify the Log Message ID is correct and exists.
    • "error": "API rate limit exceeded": Wait and retry later or optimize request frequency.
  • Resolution Tips:

    • Ensure the selected authentication method matches your Bitrix24 setup.
    • Double-check the Log Message ID input for typos or outdated values.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion