Slite
for LuumenAI
Search runbooks in Slite, then update the stale one with approval.
Luumen reads your Slite workspace the way an engineer would: search for the note, open it, walk its children, ask a plain question about what it says. When a runbook is wrong after an incident, Luumen drafts the correction, shows you the change, and updates the note once you approve. Connects with an API key.
The Slite toolbox
16 tools: 8 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadAsk QuestionAsk a question to your Slite notes in natural language.
- ReadGet authenticated userRetrieves information about the currently authenticated user.
- ReadGet Note By IDRetrieve a complete note by its ID including content in Markdown or HTML format.
- ReadGet Note ChildrenRetrieve note children by parent note ID.
- ReadList NotesList notes from Slite with optional filtering by owner.
- ReadSearch GroupsSearch for groups by name in Slite.
- ReadSearch NotesSearch notes based on a query with optional filters.
- ReadSearch UsersSearch for users in Slite by email, name, or username.
- WriteCreate NoteCreate a note from markdown or HTML content with optional template. Approval by default
- WriteDelete Note By IDPermanently delete a note and all its children by ID. Approval by default
- WriteFlag Note as OutdatedSet Outdated status on a note with a reason. Approval by default
- WriteUpdate NoteUpdate a note's content with markdown and/or title. Approval by default
- WriteUpdate Note Archived StateUpdate the archived state of a note in Slite. Approval by default
- WriteUpdate Note OwnerUpdate the owner of a note. Approval by default
- WriteUpdate Tile in NoteUpdate or create a tile within a Slite note with structured header and markdown content. Approval by default
- WriteVerify NoteSet a note's verification status to Verified with optional expiration. Approval by default
One prompt, start to finish
What a governed Slite 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 note, delete note by id, flag note as outdated, update note, 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 Slite — 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
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Slite to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.