Crisp
for LuumenAI
Read Crisp conversations for context, then reassign or reply as an approved step
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.
The Crisp toolbox
12 tools: 7 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ConversationGet one conversation's status, assignment, inbox, visitor metadata, unread counts, and latest-message summary.
- ReadGet People ProfileGet one customer profile by its Crisp people ID or exact email address.
- ReadList Conversation MessagesReturn a batch of messages from a conversation, optionally before, after, or around one millisecond timestamp.
- ReadList ConversationsList or search workspace conversations with support-focused filters, one page at a time.
- ReadList InboxesList configured Crisp inboxes and their operator/team membership, one page at a time.
- ReadList OperatorsList workspace operators and pending members with their IDs, roles, and current availability.
- ReadList People ProfilesList or search customer profiles by text, creation date, and sort order, one page at a time.
- WriteAssign ConversationAssign a conversation to one operator or explicitly remove its current operator assignment. Approval by default
- WriteMove Conversation to InboxMove a conversation to a specific Crisp inbox, or remove its inbox categorization when inbox_id is null. Approval by default
- WriteSend Conversation MessageSend a visitor-visible text reply to an existing Crisp conversation immediately; this external communication is irreversible. Approval by default
- WriteUpdate Conversation MetaUpdate support-relevant visitor details, subject, segments, or custom data on a conversation without replacing unspecified fields. Approval by default
- WriteUpdate Conversation StateSet a conversation to pending, unresolved, or resolved. Approval by default
One prompt, start to finish
What a governed Crisp run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — assign conversation, move conversation to inbox, send conversation message, update conversation meta, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Crisp — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put Crisp to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.