Stackby
for LuumenAI
Read your Stackby tables for context, and write rows back as approved steps.
Teams keep runbooks, asset inventories, and change logs in Stackby. Connect it with an API key and Luumen can read workspaces, stacks, tables, views, columns, and rows while it works on something else. When a row needs to be created, updated, or removed, it shows you the exact change first and waits for your approval.
The Stackby toolbox
9 tools: 6 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadList ColumnsList columns and their types for a Stackby table so row field names can be chosen correctly.
- ReadList RowsList one page of rows from a Stackby table, or retrieve specific rows by ID, with optional filtering, view selection, and single-field sorting.
- ReadList StacksList accessible Stackby stacks in a known workspace and return IDs needed for table discovery.
- ReadList TablesList tables in a Stackby stack and return their IDs and names.
- ReadList ViewsReturn view IDs and names for a Stackby table for use in view-scoped row queries.
- ReadList WorkspacesList accessible Stackby workspaces and return the workspace IDs needed to discover stacks.
- WriteCreate RowsCreate 1 to 10 rows in a Stackby table in one request. Approval by default
- WriteDelete RowsDelete 1 to 10 identified rows from a Stackby table. Approval by default
- WriteUpdate RowsPartially update 1 to 10 existing Stackby rows in one request. Approval by default
One prompt, start to finish
What a governed Stackby run looks like inside Luumen.
Questions
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 rows, delete rows, update rows — 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 Stackby — 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 Stackby to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.