Ninox
for LuumenAI

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.

The Ninox toolbox

4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet DatabasesRetrieves all databases within a specific Ninox team.
  • ReadGet TeamRetrieves data from a single team (workspace) by its ID.
  • ReadList TeamsRetrieves all workspaces (teams) accessible to the authenticated user.
  • WriteDelete RecordDelete a record from a specified table. Approval by default

One prompt, start to finish

What a governed Ninox run looks like inside Luumen.

Questions

How does LuumenAI connect to Ninox?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Ninox on its own?

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.

Who gets access to the integration?

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.

Is there an audit trail?

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.

Put Ninox to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.