Send meeting bots, read transcripts and chat, and manage calendar connections
Recall.ai puts meeting recordings and conversation data behind one API. Luumen reads your bots, calendars, scheduled events, chat logs, and recording artifacts on request, so you can see which meeting is covered and which one is not. Sending a bot into a call, connecting a calendar, or deleting stored media is previewed first and runs after you approve.
63 tools: 35 read, 28 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Recall.ai run looks like inside Luumen.
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 bot, create calendar integration, create calendar authentication token, create google login, and more — is shown as a plan and requires approval by default, including the 9 actions 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 Recall.ai — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.