Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically focusing on managing "Open Lines" sessions. The "Close Session" operation allows users to close an active open line session by providing its session ID. This is useful in scenarios where a chat or communication session needs to be programmatically ended, such as after a customer support interaction concludes or when automating workflow cleanups.

Practical examples include:

  • Automatically closing a live chat session once a support ticket is resolved.
  • Ending a customer conversation session after a timeout or inactivity period.
  • Integrating session closure into broader CRM automation workflows.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended for production), Webhook (simpler but less secure), or API Key authentication.
Session ID The unique identifier of the open line session to be closed. This is required to specify which session to close.
Options Additional optional parameters:
- Filter: JSON object to filter results (usage depends on operation context).
- Sort: JSON object to define sorting order for results.

Output

The node outputs JSON data representing the result of the close session operation. Typically, this will include confirmation that the session was successfully closed or details about any error encountered.

If the operation fails 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 valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • The node relies on Bitrix24's API endpoints to perform operations; thus, network connectivity and proper API permissions are necessary.
  • No additional external services beyond Bitrix24 are required.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials can cause authorization failures.
    • Providing an incorrect or non-existent Session ID will result in errors indicating the session cannot be found.
    • Network issues or Bitrix24 API downtime may cause request failures.

  • 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 error messages might include "Session not found," "Unauthorized," or "Invalid parameters."

  • Resolutions:

    • Verify that the authentication method and credentials are correctly configured and valid.
    • Ensure the Session ID corresponds to an active session.
    • Check network connectivity and Bitrix24 service status.
    • Use the "continue on fail" option to handle errors gracefully within workflows.

Links and References

Discussion