Send message with the Crisp API

Sends a message as an operator in a conversation. type text goes to the visitor right away; type note is an internal note seen only by operators.

Identifier
crisp_send_message

The request

POST https://connect.reportei.com/api/tools/crisp_send_message/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "website_id": "<website_id>",
    "session_id": "<session_id>",
    "type": "text",
    "from": "operator",
    "origin": "chat",
    "content": "<content>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
website_idstringYesId of the workspace, from List websites.
session_idstringYesId of the conversation, starting with session_, from List conversations.
typestringYestext for a message to the visitor, note for an internal note.Values: text, note
fromstringYesSender of the message. Always operator.Values: operator
originstringYesChannel of the message: chat for the chatbox, email for conversations that came in by email.Values: chat, email
contentstringYesText of the message or of the note.
userobjectNoSender shown on the message.
mentionsarrayNoOperators to mention in a note: the user_id inside details, from List operators.
attachmentsarrayNoFiles already hosted at a public URL, from 1 to 10.

Supported connections

Your customer connects their Crisp account once, with one of the modes below. The same connection serves every tool of the toolkit.

Username and password

Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/crisp_send_message. It becomes your agent's tool definition with no conversion.

Other Crisp tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.