Read your Ninox teams and databases, and delete records as an approved step
Ninox holds the custom databases your team built to track what the standard tools don't — asset inventories, change logs, vendor records. Luumen connects with an API key, lists the teams you can reach, and reads the databases inside them. When a record has to go, the deletion is previewed and held for your approval first.
4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Ninox 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 — delete record — 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 Ninox — 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.