---
title: "Crisp integration for LuumenAI"
url: "https://www.luumen.ai/integrations/crisp/"
entity: SoftwareIntegration
category: "ITSM & ticketing"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Crisp integration for LuumenAI

Read Crisp conversations for context, then reassign or reply as an approved step

## What LuumenAI can do with Crisp

LuumenAI connects to Crisp with an API token and exposes 12 tools (7 read-only · 4 write · 1 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 12 tools (7 read-only · 4 write · 1 destructive)
- Plan: available on all plans
- Category: ITSM & ticketing

## About Crisp with LuumenAI

Connect Crisp and Luumen can read your support inbox the way a lead would: open conversations, their message history, the customer profile behind them, and which operators are on shift. When something needs to change — an assignment, an inbox move, a state update, a reply to the visitor — Luumen shows the exact change first and waits for your approval. Authentication is by API key.

## Example tools

Read-only (7 in total):

- `CRISP_GET_CONVERSATION` — Get one conversation's status, assignment, inbox, visitor metadata, unread counts, and latest-message summary.
- `CRISP_GET_PEOPLE_PROFILE` — Get one customer profile by its Crisp people ID or exact email address.
- `CRISP_LIST_CONVERSATION_MESSAGES` — Return a batch of messages from a conversation, optionally before, after, or around one millisecond timestamp.
- `CRISP_LIST_CONVERSATIONS` — List or search workspace conversations with support-focused filters, one page at a time.
- `CRISP_LIST_INBOXES` — List configured Crisp inboxes and their operator/team membership, one page at a time.
- `CRISP_LIST_OPERATORS` — List workspace operators and pending members with their IDs, roles, and current availability.
- `CRISP_LIST_PEOPLE_PROFILES` — List or search customer profiles by text, creation date, and sort order, one page at a time.

Write and destructive (5 in total, approval required by default):

- `CRISP_ASSIGN_CONVERSATION` — Assign a conversation to one operator or explicitly remove its current operator assignment.
- `CRISP_MOVE_CONVERSATION_TO_INBOX` — Move a conversation to a specific Crisp inbox, or remove its inbox categorization when inbox_id is null.
- `CRISP_SEND_CONVERSATION_MESSAGE` — Send a visitor-visible text reply to an existing Crisp conversation immediately; this external communication is irreversible.
- `CRISP_UPDATE_CONVERSATION_META` — Update support-relevant visitor details, subject, segments, or custom data on a conversation without replacing unspecified fields.
- `CRISP_UPDATE_CONVERSATION_STATE` — Set a conversation to pending, unresolved, or resolved.

## Frequently asked questions

### How does LuumenAI connect to Crisp?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Crisp on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to Crisp — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/crisp/