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 → Update State
AI-generatedOverview
This node operation updates the state of a conversation in the Crisp platform. It is useful for managing the status of customer conversations, such as marking them as resolved, unresolved, or pending. For example, a support team can use this operation to automatically update the conversation state after resolving a customer's issue.
Use Case Examples
- Automatically mark a conversation as resolved after a support ticket is closed.
- Set a conversation state to pending when waiting for customer response.
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 update. |
| Additional Fields | Optional fields to update the conversation state, including state (resolved, unresolved, pending), blocking status, assignment to user ID, role, and other metadata. |
Output
JSON
state- The updated state of the conversation (resolved, unresolved, pending).
Dependencies
- Crisp API credentials (username and password) for authentication.
Troubleshooting
- Ensure the Website ID and Session ID are correct and correspond to existing Crisp website and conversation.
- Verify that the API credentials are valid and have sufficient permissions to update conversation state.
- Check that the 'state' field in Additional Fields is set to a valid value (resolved, unresolved, pending).
- Handle API errors gracefully, especially network issues or invalid request payloads.
Links
- Crisp API - Update Conversation State - Official Crisp API documentation for updating conversation state.