This article explains how Web Hooks help you receive real-time Crisp events on your own endpoint.

Web Hooks are useful when you want Crisp to notify another system whenever something happens in your workspace, for example when a visitor sends a message or a conversation changes. For developer-heavy integrations, start from the Developer Hub so you can pick the right hook type and event namespaces.

How Crisp Web Hooks work

Crisp sends Web Hooks as JSON payloads over HTTP POST. Instead of polling the REST API repeatedly, your endpoint receives an event when Crisp has something to report.

Crisp supports two Web Hook families:

• Website Hooks → configured for one workspace from Crisp in Settings → Website Settings → Advanced Configuration → Webhooks
• Plugin Hooks → configured from a private or public plugin in the Crisp Marketplace

Plugin Hooks are generally the best option for integrations that need reliability or distribution across multiple workspaces, as they support more event namespaces, retries, and signed payloads.

When to use each option

Use Website Hooks for simple internal automation

Website Hooks are the quickest way to connect a single Crisp workspace to your own endpoint, a no-code automation tool, or an internal system.

Use Plugin Hooks for production integrations

Plugin Hooks are designed for integrations built on top of the Crisp Marketplace. They are a better fit when your service is installed by multiple Crisp workspaces, or when you need stronger delivery and authentication guarantees.

Developer documentation

Updated on: 03/05/2026