Actions64
- Website Actions
- Conversation Actions
- People Actions
- Operator Actions
- Settings Actions
- Analytics Actions
- Availability Actions
- Campaign Actions
- Helpdesk Actions
- Visitors Actions
- Batch Actions
- Verify Actions
Batch → Remove Conversations
AI-generatedOverview
This node operation allows batch removal of conversations from a specified Crisp website. It is useful for managing and cleaning up multiple conversations at once, based on criteria defined in the additional fields. For example, a user can remove all conversations that meet certain conditions such as being unresolved or associated with a specific email or company.
Use Case Examples
- Batch remove conversations from a Crisp website by specifying the website ID and filtering criteria such as conversation state or assigned user ID.
- Clean up old or irrelevant conversations in bulk to maintain an organized Crisp dashboard.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, used to identify which website's conversations to remove. |
| Additional Fields | Optional filters and parameters to specify which conversations to remove, such as email, first name, last name, phone, company, conversation state, blocked status, assigned user ID, operator role, domain, and verification string. |
Output
JSON
operation- The batch operation details sent to the API for removing conversations.response- The response from the Crisp API after attempting to remove the batch of conversations.
Dependencies
- Crisp API with API key credentials
Troubleshooting
- Ensure the Website ID is correct and corresponds to an active Crisp website.
- Verify that the API credentials (username and password) are valid and have the necessary permissions.
- Check that the additional fields used for filtering are correctly formatted and valid according to Crisp API specifications.
- If the batch removal fails, the node may return error messages from the Crisp API indicating issues such as invalid parameters or authorization errors.