Grist
for LuumenAI

Read Grist tables for context, then add or update records as approved steps

Operations teams keep a lot in Grist: on-call rosters, asset inventories, change logs, vendor lists. Luumen connects with an API key and reads your documents, tables, columns, and records directly in the terminal. When something needs to change, it shows the rows it plans to write and waits for your approval first.

The Grist toolbox

30 tools: 14 read, 16 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadDownload All Attachments ArchiveDownload all attachments from a Grist document as a single archive file (.zip or .tar).
  • ReadDownload AttachmentDownload a file attachment from a Grist document.
  • ReadFetch Document MetadataFetch metadata for a specified Grist document.
  • ReadFetch Table MetadataRetrieve metadata for a specified table in a Grist document.
  • ReadGet Org AccessRetrieves the list of users who have access to a Grist organization along with their access roles (owners, editors, viewers).
  • ReadGet UsersRetrieve a list of users via SCIM v2.
  • ReadList AttachmentsList all attachments in a Grist document.
  • ReadList ColumnsList all columns in a specified Grist table.
  • ReadList OrganizationsList all organizations accessible to the authenticated user.
  • ReadList RecordsRetrieve records from a specified table within a Grist document.
  • ReadList TablesList all tables within a specified document.
  • ReadList WebhooksList all webhooks configured for a Grist document.
  • ReadList WorkspacesList all workspaces and documents accessible to the authenticated user on the current site.
  • ReadRun SQL QueryExecute a read-only SQL SELECT query on a Grist document.
  • WriteAdd RecordsAdd one or more records to a Grist table. Approval by default
  • WriteCreate DocumentCreates a new Grist document in a specified workspace. Approval by default
  • WriteCreate SCIM UserCreate a new SCIM user. Approval by default
  • WriteCreate TableCreate tables in a document. Approval by default
  • WriteCreate Document WebhookCreate a new webhook for a specified document. Approval by default
  • WriteRemove Unused AttachmentsRemove unused attachments from a Grist document to free up storage space. Approval by default
  • WriteDelete ColumnDelete a column from a Grist document table. Approval by default
  • WriteDelete Grist Table RecordsDelete records from a specified Grist table. Approval by default
  • WriteDelete SCIM UserDelete a user from the Grist organization by their numeric user ID. Approval by default
  • WriteDelete WebhookPermanently removes a webhook from a Grist document. Approval by default
  • WriteUpdate Column MetadataUpdates metadata (label, type, description, formula, etc.) for one or more columns in a Grist table. Approval by default
  • WriteUpdate Document MetadataUpdate metadata for a specified Grist document. Approval by default
  • WriteUpdate RecordsUpdate existing records in a Grist table by their row IDs. Approval by default
  • WriteUpdate Table MetadataUpdate metadata properties for a table in a Grist document. Approval by default
  • WriteUpdate WebhookUpdate an existing webhook configuration for a Grist document. Approval by default
  • WriteUpload AttachmentUpload one or more file attachments to a Grist document. Approval by default

One prompt, start to finish

What a governed Grist run looks like inside Luumen.

Questions

How does LuumenAI connect to Grist?

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

Read actions answer immediately. Anything that writes — add records, create document, create scim user, create table, and more — is shown as a plan and requires approval by default, including the 5 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 Grist — 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 Grist to work with Luumen

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