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 → Process Button Action
AI-generatedOverview
The node processes a button action within a Crisp conversation. It executes a configured response based on the type of button action selected, such as sending a message, picker, field, carousel, closing the conversation, transferring to an agent, or triggering a custom webhook. This is useful for automating interactive responses in chat conversations, enhancing user engagement and support workflows.
Use Case Examples
- Sending a predefined message when a user clicks a button in a chat widget.
- Presenting a picker with multiple choices for the user to select from.
- Closing a conversation automatically after a button action.
- Transferring the conversation to a specific agent based on button interaction.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the website for the conversation. |
| Session ID | The session ID of the conversation to process the button action on. |
| Button Action Type | The type of action to execute when the button is pressed, such as sending a message, picker, field, carousel, closing the conversation, transferring to an agent, or custom webhook. |
| Action Configuration | JSON configuration for the action, including message content, picker options, carousel targets, agent ID for transfer, or webhook URL and data. |
| Additional Fields | Optional additional fields such as email, first name, last name, phone, company, conversation state, blocking status, assignment to user ID, operator role, domain, and verification string. |
Output
JSON
type- Type of the processed button action message (e.g., text, picker, field, carousel).from- Sender of the message, typically 'operator'.origin- Origin of the message, typically 'chat'.content- Content of the message or action configuration executed.
Dependencies
- Crisp API credentials (username and password) for Basic Authentication
Troubleshooting
- Ensure the Website ID and Session ID are correct and correspond to an active conversation.
- Verify that the JSON in the Action Configuration is valid and correctly formatted.
- If sending picker or carousel messages, ensure the choices or targets arrays are properly structured and not empty.
- Check API credentials and permissions to confirm the node can perform the requested actions.
- Common errors include invalid JSON, missing required fields (like picker ID and text), or unauthorized API access.