Read your NocoDB bases for context, then change views as approved steps
NocoDB puts a spreadsheet interface and REST API over your databases. Luumen connects with an API key, reads table schemas, view configuration, workspaces, and instance health on demand, and answers from what is actually there. Changes like updating a view column or storing integration config are previewed first, then applied.
28 tools: 18 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed NocoDB 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.
This connection exposes write actions such as forgot password, sign out user, update view column, delete view, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 NocoDB — 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.