Hex
for LuumenAI

Read Hex projects, runs, and sharing — change access as an approved step

Connect Hex and Luumen can read your workspace the way an analyst would: which projects exist, who is in which group, what a scheduled run did last night, and which cells make up a draft. When something needs to change — sharing a project with a group, creating a collection, canceling a stuck run — Luumen shows the change first and waits for your approval. Auth is by API key.

The Hex toolbox

32 tools: 13 read, 19 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet CellGet a single cell by ID from the draft version of a Hex project.
  • ReadGet collectionGet information about a specific collection in Hex.
  • ReadGet GroupRetrieve information about a specific Hex group.
  • ReadGet ProjectGet metadata about a single Hex project.
  • ReadGet Project RunsRetrieve the status of API-triggered runs for a specific Hex project.
  • ReadGet Run Chart ImageRetrieve a rendered chart image from a Hex project run.
  • ReadGet Run StatusRetrieve the status of a specific Hex project run.
  • ReadList CellsList all cells from the draft version of a Hex project.
  • ReadList CollectionsRetrieve all collections in the workspace with pagination support.
  • ReadList Data ConnectionsList all data connections in the Hex workspace with pagination support.
  • ReadList groupsList all groups in the Hex workspace with pagination support.
  • ReadList Hex ProjectsList all viewable Hex projects with pagination and filtering support.
  • ReadList UsersList all users in the Hex workspace with pagination support.
  • WriteCancel RunCancel a project run that is in progress. Approval by default
  • WriteCreate CellCreate a new cell in the draft version of a Hex project. Approval by default
  • WriteCreate CollectionCreate a new collection in the Hex workspace. Approval by default
  • WriteCreate GroupCreate a new group in the Hex workspace. Approval by default
  • WriteDeactivate UserDeactivates a user in the Hex workspace. Approval by default
  • WriteDelete CellPermanently delete a cell from the draft version of a project. Approval by default
  • WriteDelete GroupDeletes a group from the Hex workspace. Approval by default
  • WriteDelete Guide DraftDeletes a guide draft by ID from Hex. Approval by default
  • WriteEdit CollectionEdit a collection's name, description, and sharing settings in Hex. Approval by default
  • WriteEdit GroupEdit a group's name and/or members in Hex. Approval by default
  • WriteEdit Project Sharing CollectionsAdd a project to collections or remove it from collections. Approval by default
  • WriteEdit Project Sharing GroupsEdit project sharing settings for groups in Hex. Approval by default
  • WriteEdit Project Sharing SettingsEdit project sharing settings for workspace members and public web access. Approval by default
  • WriteEdit Project Sharing UsersEdit project sharing settings for individual users in Hex. Approval by default
  • WritePublish Guide DraftsPublish all currently drafted guides or specific guides by ID. Approval by default
  • WriteRun ProjectTrigger a run of the latest published version of a Hex project. Approval by default
  • WriteUpdate CellUpdate a cell's source code and/or data connection in Hex. Approval by default
  • WriteUpdate Project StatusAdd or remove a status (including endorsements) from a Hex project. Approval by default
  • WriteUpsert Guide DraftUpdate or create guide drafts by filePath. Approval by default

One prompt, start to finish

What a governed Hex run looks like inside Luumen.

Questions

How does LuumenAI connect to Hex?

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

Read actions answer immediately. Anything that writes — cancel run, create cell, create collection, create group, 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.

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 Hex — 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 Hex to work with Luumen

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