Read, draft, and update Google Docs runbooks without leaving the terminal
Connect Google Docs and Luumen can read the documents your team already relies on — runbooks, postmortems, change records — and pull them into a session as context. It can also draft new documents, copy templates, and add tables, headers, and footnotes. Reads happen right away. Changes are previewed and held for your approval first.
41 tools: 6 read, 35 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Google Docs run looks like inside Luumen.
Authorize once with OAuth 2.0. 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 — copy google document, create and populate table in google doc, create a document, create document markdown, and more — is shown as a plan and requires approval by default, including the 8 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 Google Docs — 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.