Read Grist tables for context, then add or update records as approved steps
Operations teams keep a lot in Grist: on-call rosters, asset inventories, change logs, vendor lists. Luumen connects with an API key and reads your documents, tables, columns, and records directly in the terminal. When something needs to change, it shows the rows it plans to write and waits for your approval first.
30 tools: 14 read, 16 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Grist 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 — add records, create document, create scim user, create table, and more — is shown as a plan and requires approval by default, including the 5 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 Grist — 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.