Crisp icon

Crisp

Interact with Crisp API - Complete integration with all available endpoints

Actions64

Conversation → Remove

AI-generated

Overview

This node operation removes a conversation from a specified website in the Crisp platform. It is useful for managing and cleaning up conversations that are no longer needed or relevant. For example, a customer support team might use this operation to delete resolved or spam conversations to keep their dashboard organized.

Use Case Examples

  1. Removing a conversation by providing the website ID and the session ID of the conversation to be deleted.
  2. Automating the cleanup of old conversations in a Crisp website through workflow automation.

Properties

Name Meaning
Website ID The website ID from your Crisp dashboard, identifying the website where the conversation exists.
Session ID The session ID of the conversation to be removed.
Additional Fields Optional fields that can include email, first name, last name, phone, company, state (resolved, unresolved, pending), blocked status, user assignment, role, domain, and verification string to provide more context or control over the conversation removal.

Output

JSON

  • response - The response from the Crisp API after attempting to remove the conversation, typically confirming success or failure.

Dependencies

  • Crisp API credentials (username and password) for authentication.

Troubleshooting

  • Ensure the Website ID and Session ID are correct and correspond to existing entities in Crisp; otherwise, the API call will fail.
  • Check that the API credentials provided have sufficient permissions to delete conversations.
  • If the operation fails, the node may return an error message from the Crisp API indicating the reason, such as invalid session ID or insufficient permissions.

Links

Discussion