Read Softr databases and tables, and change records as approved steps
Softr holds the data behind your client portals and internal tools. Connect it and Luumen can list databases, open tables and views, and search records while you work a ticket. When something needs to change — a record updated, a field added, a table created — Luumen shows the plan first and waits for your approval. Authentication is by API key.
21 tools: 9 read, 12 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Softr 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 — create database, create record, create table, create table field, and more — is shown as a plan and requires approval by default, including the 4 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 Softr — 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.