Crisp icon

Crisp

Interact with Crisp API - Complete integration with all available endpoints

Actions64

Conversation → Widget Button Action

AI-generated

Overview

This node operation allows sending a widget button action to a specific conversation in the Crisp chat system. It is useful for automating interactions triggered by widget button clicks on a website, such as sending data or triggering specific workflows based on user actions within a chat session.

Use Case Examples

  1. Automate sending a widget button click event to a conversation when a user interacts with a chat widget button on your website.
  2. Trigger backend workflows or notifications by delivering widget button actions from the chat interface to Crisp's conversation system.

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 which the widget button action will be delivered.
Widget Button ID The ID of the widget button that was clicked or interacted with.
Widget Button Data Optional JSON string containing additional data related to the widget button action.
Additional Fields Optional additional metadata fields such as email, first name, last name, phone, company, conversation state, block status, assignment user ID, role, domain, and verification string to provide more context or control over the conversation state.

Output

JSON

  • id - The ID of the widget button action response from the Crisp API
  • data - The data sent with the widget button action, if any
  • statusCode - HTTP status code of the API response
  • message - Response message or error message if the action failed

Dependencies

  • Requires 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 in Crisp.
  • Verify that the Widget Button ID is valid and exists in the Crisp widget configuration.
  • If providing Widget Button Data, ensure it is a valid JSON string to avoid parsing errors.
  • Check API credentials and permissions to confirm the node can authenticate and send requests to the Crisp API.
  • Common errors include invalid session or website IDs, malformed JSON in widget button data, and authentication failures. Verify these inputs to resolve issues.

Links

Discussion