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 → Unblock
AI-generatedOverview
This node operation unblocks a conversation in the Crisp platform, allowing the user to send messages again after being previously blocked. It is useful in scenarios where a conversation was blocked to prevent user messages but now needs to be reopened for communication.
Use Case Examples
- Unblocking a conversation after resolving an issue with a user.
- Allowing a user to resume messaging after a temporary block.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the Crisp website instance. |
| Session ID | The session ID of the conversation to unblock. |
| Additional Fields | Optional additional fields related to the conversation, such as email, first name, last name, phone, company, state, blocked status, assigned user ID, role, domain, and verification string. |
Output
JSON
blocked- Indicates if the conversation is blocked (false after unblock)sessionId- The session ID of the conversation that was unblockedstatusCode- HTTP status code of the unblock request responsemessage- Response message or details from the unblock operation
Dependencies
- Crisp API credentials (username and password) for Basic Authentication
Troubleshooting
- Ensure the Website ID and Session ID are correct and correspond to an existing conversation.
- Check that the Crisp API credentials are valid and have the necessary permissions.
- If the conversation is not unblocked, verify that the conversation was previously blocked and that the API endpoint is reachable.
- Handle errors returned by the API gracefully, especially network or authentication errors.