Integration · Sell and serve

Crisp and Meteor AI agents

Connect Crisp to a WhatsApp Met: find conversations and contacts, read your knowledge base, leave internal notes and move chats between inboxes.

Book a demo See every integration

How does Crisp connect to Meteor?

With the Crisp ready connector, your WhatsApp Met reads and writes in your company's Crisp workspace with the MCP token the admin pastes. It finds an article in your knowledge base and reads it in full to answer, finds the contact by name or email and reviews their conversations in your website chat. If the admin leaves it on, it also leaves internal notes, replies in a Crisp conversation, changes its state or moves it to another inbox, and updates the contact's segments. It is Crisp's official server: usage runs on your Crisp account.

What it automates

What a Meteor Met does with Crisp

Answer from your knowledge base

When a customer asks something already written in your Crisp knowledge base, the Met finds the article by title, reads it in full and answers with it. If you change the article, the answer changes.

Know whether the customer already wrote through the website chat

The Met finds the contact by name or email, lists their Crisp conversations and reads the recent messages, so it does not ask again what they already said in your website chat.

Leave context for the team in Crisp

If the case continues in Crisp, the Met leaves an internal note with what was said on WhatsApp and moves the conversation to the inbox of the team that should handle it.

Segment the contact

The Met updates the contact's segments in the Crisp CRM based on what they asked for, so your team finds them in its filters.

23 tools

Everything your Met can ask Crisp for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`get_website_information`	Returns the basic information of the connected Crisp workspace.
`get_availability_status`	Tells whether your website chat shows as online or offline.
`list_operators`	Lists the team members who are operators in the workspace.
`list_operators_active`	Lists the operators who are active right now in a Crisp app.
`list_inboxes`	Lists the workspace inboxes, which group conversations.
`list_latest_conversations`	Lists the workspace's most recent conversations.
`search_conversations`	Searches conversations by message content or by segments.
`get_conversation`	Returns a conversation's data and metadata.
`list_latest_conversation_messages`	Lists a conversation's recent messages.
`send_conversation_message_text`	Sends a text message the customer sees in an open Crisp conversation.
`send_conversation_message_note`	Leaves an internal note on a conversation; only your team sees it.
`change_conversation_state`	Changes a conversation's state to resolved, unresolved or pending.
`move_conversation_inbox`	Moves a conversation to another inbox.
`search_people_profiles`	Searches Crisp CRM contacts by full name or email.
`get_people_profile`	Returns the full details of a Crisp CRM contact.
`list_people_conversations`	Lists the conversations linked to a contact.
`update_people_profile_segments`	Updates a contact's segments.
`get_helpdesk_information`	Returns your knowledge base's name and address.
`list_helpdesk_pages`	Lists the knowledge base's published pages with their address.
`list_helpdesk_tree`	Lists the knowledge base file tree.
`search_helpdesk_tree`	Searches for a knowledge base file by its title.
`get_helpdesk_tree_path_content`	Returns the content of a knowledge base file.
`get_helpdesk_tree_path_title`	Returns the title of a knowledge base file.

The limits

What the Crisp integration does NOT do

We would rather say it here than have you find out during rollout.

It does not use the URL with the token attached. Met sends the token only in the authorization header, even though Crisp's documentation offers the other way.
This page does not cover creating, editing or deleting knowledge base files. Those actions exist on the server: deleting starts switched off, while creating and editing arrive switched on, so turn them off in Connections if you do not want the Met to use them.
It does not ask for confirmation in the chat before writing. The admin chooses in Connections which actions stay on; Crisp marks none as destructive.
It does not open new conversations in Crisp: it sends messages and notes in a conversation that already exists.
It has no more permissions than the token: Crisp applies the same access controls to this token as to the REST API.

Before you start

What you need to connect Crisp

1

Your Crisp workspace MCP token

In Crisp, open Workspace Settings → Advanced configuration and, in the MCP server token block, generate the token. Crisp shows it only once; regenerating it also regenerates your REST API tokens.
2

Connect it in Met

In Met, open Connections → Crisp → Connect and paste the token. Then you choose which actions stay on.

Frequently asked questions

Questions about Crisp and Meteor

It can send a message in an existing Crisp conversation if that action is on. Its main job is still the WhatsApp conversation.

Crisp also regenerates the REST API tokens, and the token you pasted in Met stops working. You need to paste the new one in Connections.

This page does not include that action. It exists on the server, and since its name says it deletes, it starts switched off until the admin turns it on.

You do, with your own Crisp plan. Meteor does not resell Crisp: the connector uses your workspace's token.

Step by step