Leexi
for LuumenAI
Read call transcripts and summaries, and schedule the next meeting for recording
Leexi records, transcribes, and summarizes your calls and meetings. Connected to Luumen, the agent can pull a specific call, scan recent ones across the workspace, and check who is on which team — without you opening the app. When something needs to be booked for recording, it drafts the meeting event and waits for your approval first. Authentication is by API key.
The Leexi toolbox
9 tools: 6 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet CallGet details of a specific call or meeting by UUID from Leexi.
- ReadGet Meeting EventRetrieve a specific meeting event by UUID from Leexi.
- ReadList CallsList all calls and meetings in your Leexi workspace with pagination support.
- ReadList Meeting EventsList all meeting events in your Leexi workspace with pagination support.
- ReadList TeamsList all teams in your Leexi workspace with pagination support.
- ReadList UsersList all users in your Leexi workspace.
- WriteCreate Meeting EventCreate a new meeting event in Leexi with timing, participants, and recording preferences. Approval by default
- WriteDelete Meeting EventDelete a specific meeting event by UUID. Approval by default
- WriteRequest Presigned URLRequest a presigned URL for uploading a call recording before creating the call. Approval by default
One prompt, start to finish
What a governed Leexi 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 — create meeting event, delete meeting event, request presigned url — 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 Leexi — 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
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Leexi to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.