Crisp
Capture visitor messages from Crisp chat.
What you will need
- Webhook secret
Steps
In FeedbackFlow, open your project, go to Integrations, and select Crisp. Then:
- 1
In Crisp, go to Settings → Website Settings → Integrations → Web Hooks and add one.
- 2
Set the target URL to:
https://www.usefeedbackflow.com/api/ingest/crisp/YOUR_PROJECT_ID - 3
Subscribe to "message:send" and copy the secret into FeedbackFlow. Only text messages from visitors are ingested, not operator replies or file uploads.
Replace YOUR_PROJECT_ID with the ID of your project, shown on the integration setup screen.
What gets captured from Crisp
Text messages from the visitor. Operator messages are skipped, and so is anything that is not text: an image or a voice note carries no message to triage. The Crisp message fingerprint is the deduplication key.
Check that it worked
- Crisp signs with HMAC-SHA256 as hex in x-crisp-signature, so paste the secret for that webhook into FeedbackFlow first.
- Send a message from the visitor side of the chat rather than from the operator inbox.
- The message appears with the visitor’s email attached if Crisp has one for them.
If it is not working
- Deliveries return 401
- Crisp sends its signature as hex rather than base64, so a secret from a different webhook, or one with a stray character, fails the compare.
- Operator messages are missing
- By design. Only messages whose sender is the visitor are ingested, so a reply from your side of the same conversation is acknowledged and skipped. The visitor's side is the feedback; your answers to them are not.
- Image or voice messages never arrive
- Only text messages are ingested. A non-text payload has nothing to triage, so it is acknowledged and skipped.
Still stuck? Widget and integration troubleshooting covers the problems that are not specific to Crisp.