Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 CRM and business platform, specifically focusing on the "Timeline" resource's "Unbind" operation. The "Unbind" operation removes a previously established binding between a timeline event and a specified CRM entity (such as a Lead, Deal, Contact, or Company). This is useful when you want to dissociate timeline entries from entities, for example, cleaning up incorrect associations or managing event visibility in the CRM timeline.

Practical scenarios include:

  • Removing an outdated or incorrect link between a timeline event and a CRM record.
  • Managing timeline data by unbinding events that are no longer relevant to certain entities.
  • Automating cleanup tasks in Bitrix24 workflows where timeline bindings need to be adjusted dynamically.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Entity Type Type of CRM entity to unbind from: Lead, Deal, Contact, or Company.
Entity ID Identifier of the specific CRM entity instance to unbind the timeline event from.
Binding Data JSON object describing the binding details to remove (e.g., timeline event identifiers).
Options Additional optional parameters including:
- Filter JSON filter criteria to refine which bindings to affect.
- Order JSON specifying sort order for processing bindings.
- Start Number indicating start position for pagination if multiple bindings exist.

Output

The node outputs an array of items, each containing a json field representing the result of the unbind operation. Typically, this includes confirmation of the unbinding action or error information if the operation failed.

If the operation encounters an error and the node is configured to continue on failure, the output item will contain an error field with the error message, along with the resource name and a timestamp.

No binary data output is indicated for this operation.

Dependencies

  • Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2 token, webhook URL, or API key.
  • Relies on Bitrix24 API endpoints to perform the unbind operation.
  • No additional external services beyond Bitrix24 are required.
  • Proper configuration of credentials in n8n is necessary for successful API communication.

Troubleshooting

  • Common Issues:

    • Incorrect or missing authentication credentials leading to authorization errors.
    • Invalid or non-existent Entity ID or Entity Type causing the API to reject the unbind request.
    • Malformed JSON in the Binding Data property resulting in request failures.
    • Network connectivity issues preventing access to Bitrix24 API.

  • Error Messages:

    • Authorization errors typically indicate invalid or expired credentials; re-authenticate or update credentials.
    • Validation errors may mention missing required fields or invalid formats; verify input properties carefully.
    • API rate limits or timeouts can cause temporary failures; consider retrying after some delay.

  • Resolution Tips:

    • Double-check the Entity Type and Entity ID values correspond to existing records in Bitrix24.
    • Validate the JSON structure in Binding Data before execution.
    • Ensure the selected authentication method is correctly set up and active.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion