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
Conversation → Block
AI-generatedOverview
This node operation blocks a conversation in the Crisp chat system, preventing the user from sending messages in that conversation. It is useful in scenarios where an operator needs to temporarily or permanently restrict communication from a specific user session, such as in cases of spam or abusive behavior.
Use Case Examples
- Blocking a conversation by specifying the website ID and session ID to prevent further messages from the user.
- Using the block operation as part of a workflow to moderate chat interactions automatically.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the website associated with the conversation. |
| Session ID | The session ID of the conversation to be blocked. |
| Additional Fields | Optional fields that can include email, first name, last name, phone, company, state, blocked status, user assignment, role, domain, and verification string. For the block operation, the 'blocked' field is relevant to indicate blocking the conversation. |
Output
JSON
blocked- Indicates if the conversation is blocked (true) or unblocked (false)sessionId- The session ID of the conversation that was blockedwebsiteId- The website ID associated with the conversation
Dependencies
- Crisp API key credential
Troubleshooting
- Ensure the Website ID and Session ID are correct and correspond to an active conversation.
- The node requires valid Crisp API credentials; verify that the API key is correctly configured.
- If the conversation is already blocked, the operation may not change the state but should not error.
- Check network connectivity and API endpoint availability if requests fail.