Knack
for LuumenAI

Read and update records in your Knack apps from the terminal

Knack often ends up holding the records an operations team runs on: asset inventories, on-call rosters, change requests, vendor contacts. Connect it and Luumen can read those objects and views directly while you work, then create, update, or remove records as a step you approve first. Authentication is by API key.

The Knack toolbox

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

  • ReadGet Object RecordRetrieve a single record by its ID from a specific Knack object.
  • ReadList Object RecordsRetrieve multiple records from a specific Knack object (table).
  • ReadList View RecordsRetrieve multiple records from a specific Knack view (tables, lists, searches, calendars).
  • WriteCreate object recordCreate a new record in a specific Knack object. Approval by default
  • WriteCreate View RecordCreate a new record through a form view in Knack. Approval by default
  • WriteDelete Object RecordDelete a single record from a specific Knack object by its ID. Approval by default
  • WriteDelete View RecordDelete a record through a view that contains a delete link. Approval by default
  • WriteUpdate object recordUpdate an existing record in a specific Knack object. Approval by default
  • WriteUpload FileUpload a file to a Knack application. Approval by default
  • WriteUpload ImageUpload an image to a Knack application. Approval by default

One prompt, start to finish

What a governed Knack run looks like inside Luumen.

Questions

How does LuumenAI connect to Knack?

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 Knack on its own?

Read actions answer immediately. Anything that writes — create object record, create view record, delete object record, delete view record, and more — is shown as a plan and requires approval by default, including the 2 actions 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 Knack — 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 Knack to work with Luumen

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