Crisp

This connector uses the Crisp REST API v1 (docs.crisp.chat/api/v1/).

Setup:

1. Sign in to Crisp → Marketplace → Create a Plugin (the modern way for API access; the legacy User token approach is deprecated).
2. Pick scopes: at minimum website:conversation:read, website:conversation:write, website:people:read.
3. After creating + reviewing, you get plugin_id, plugin_identifier, plugin_key (the credentials).
4. Install the plugin on your website (give it a website_id to act on).
5. Set:
   • CRISP_PLUGIN_IDENTIFIER = the identifier
   • CRISP_PLUGIN_KEY = the key
   • CRISP_WEBSITE_ID = the website ID to operate on

Authentication: HTTP Basic with username=PLUGIN_IDENTIFIER + password=PLUGIN_KEY + custom header X-Crisp-Tier: plugin on every request.

Conversation model: every conversation has a session_id (unique per chat). Messages live inside a conversation, ordered chronologically.

Session vs People: Crisp tracks people (long-lived contact profiles) and sessions (single chat). A session attaches to a people record by email/phone/segment matching.

Message origins: chat, email, sms, twitter, facebook, instagram, whatsapp, telegram, slack, messenger, line, etc. Crisp normalizes them in the same conversation thread.

Rate limits: 100 req per 10 sec per website. On 429 back off.

Out of scope here: plugin management, RTM/WebSocket events, MagicType (AI-generated reply suggestions), Crisp Status (status page), Triggers.