# Crisp integrations: conversations and messages

> Create a conversation, send a message and add a profile in Crisp, and start a workflow when Crisp sends “Message sent”.

**Canonical page:** https://tray.ai/connectors/crisp-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

Crisp is a customer messaging platform that puts website chat, email, and social conversations in one shared inbox, alongside contact profiles and campaigns. Tray.ai connects to Crisp through the HTTP Connector, so your workflows can call the Crisp API alongside the rest of your stack.

## Use cases

### Conversations

Read, create, update, and delete conversations in Crisp from any Tray.ai workflow. The Crisp API covers calls such as list conversations and create a conversation.

- List conversations
- Create a conversation
- Get a conversation

### Messages

Create and update messages in Crisp from any Tray.ai workflow. The Crisp API covers calls such as send a message and update a message.

- Send a message
- Update a message

### People profiles

Read, create, update, and delete people profiles in Crisp from any Tray.ai workflow. The Crisp API covers calls such as list people profiles and add a profile.

- List people profiles
- Add a profile
- Update a profile

### Visitors

Read visitors in Crisp from any Tray.ai workflow. The Crisp API covers calls such as count visitors and list visitors.

- Count visitors
- List visitors

### Campaigns

Read, create, update, and delete campaigns in Crisp from any Tray.ai workflow. The Crisp API covers calls such as list campaign templates and create a campaign template.

- List campaign templates
- Create a campaign template
- Update a campaign template

### Crisp events

Start a Tray.ai workflow the moment something happens in Crisp. Crisp sends events such as message sent and message received to a Tray.ai webhook trigger.

- Message sent
- Message received
- Conversation state changed

## Challenges Tray.ai solves

### Keeping Crisp credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Crisp credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Crisp API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Crisp API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Crisp?

Yes. Tray.ai connects to Crisp through the HTTP Connector, which calls the Crisp API directly. Any call the Crisp API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Crisp?

The Crisp API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Crisp connector?

Crisp runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Crisp connector from the Crisp API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/