Crisp icon

Crisp

Interact with Crisp API - Complete integration with all available endpoints

Actions64

Conversation → Send Message

AI-generated

Overview

This node operation sends a message within a specified conversation on a Crisp website. It supports various message types including text, note, picker (button options), field (input), carousel, and event. The node is useful for automating communication in customer support or chat scenarios, allowing operators to send different interactive message formats to users in a conversation.

Use Case Examples

  1. Sending a simple text message to a user in a conversation.
  2. Sending a picker message with multiple button options for user interaction.
  3. Sending a carousel message with multiple items and links.
  4. Sending an event message with custom event data.

Properties

Name Meaning
Website ID The website ID from your Crisp dashboard, identifying the Crisp website.
Session ID The session ID of the conversation where the message will be sent.
Message The content of the message to send (used for text and other simple message types).
Message Type The type of message to send, such as text, note, picker, field, carousel, or event.
Picker ID Unique identifier for the picker (required if message type is picker).
Picker Text Text to display with the picker (required if message type is picker).
Picker Choices Choice options for the picker, each with value, label, icon, action type, and other configurations.
Field ID Unique identifier for the field (required if message type is field).
Field Text Text to display for the field (required if message type is field).
Field Explanation Additional explanation text for the field.
Field Required Whether the field is required to be filled by the user.
Carousel Targets Carousel items, each with title, description, action type, and action target URL.
Event Type Type of event to send (used if message type is event).
Event Data Event data as a JSON string (used if message type is event).

Output

JSON

  • type - The type of the sent message (e.g., text, picker, field, carousel, event).
  • from - The sender of the message, typically 'operator'.
  • origin - The origin of the message, typically 'chat'.
  • content - The content of the message, structure varies by message type.

Dependencies

  • Crisp API with API key credentials

Troubleshooting

  • Ensure the Website ID and Session ID are correct and correspond to an active Crisp website and conversation session.
  • For picker messages, ensure at least one valid choice with both value and label is provided, and that picker ID and text are set.
  • For field messages, ensure field ID and text are provided.
  • For carousel messages, ensure at least one valid target with title and description is provided.
  • If sending event messages, ensure the event data is valid JSON if provided.
  • Check API credentials and permissions if requests fail with authorization errors.
  • Handle errors returned by the Crisp API, such as invalid parameters or missing required fields.

Links

Discussion