Boxhero
for LuumenAI

Read BoxHero stock, locations, and transactions; delete records with approval.

Connect BoxHero with an API key and your team's inventory becomes something you can ask about in plain language. Check an item by barcode, list warehouse locations, review basic or location-mode transactions, and see who is on the team. Cleanup work — deleting a retired item or an unused location — is previewed and held for approval before anything is removed.

The Boxhero toolbox

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

  • ReadGet ItemRetrieve a specific item (barcode) by ID.
  • ReadGet Item AttributeRetrieve a specific item attribute by ID.
  • ReadGet LocationRetrieve a specific location by ID.
  • ReadGet MemberRetrieve a specific team member by ID.
  • ReadGet Linked Team InfoGet information about the linked team and its mode.
  • ReadBoxHero - List Basic TransactionsList basic inventory transactions.
  • ReadList Item AttributesRetrieve the list of item attribute specifications used within the team.
  • ReadList ItemsList items.
  • ReadBoxHero - List LocationsList warehouse locations.
  • ReadBoxHero - List Location TransactionsRetrieve the list of transactions in location mode.
  • ReadList Team MembersRetrieve the list of team members.
  • ReadBoxHero - List PartnersList partners (suppliers and customers).
  • WriteDelete ItemDelete a specific item (barcode) by its ID. Approval by default
  • WriteBoxHero - Delete LocationDelete a specific warehouse location by its ID. Approval by default

One prompt, start to finish

What a governed Boxhero run looks like inside Luumen.

Questions

How does LuumenAI connect to Boxhero?

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

Read actions answer immediately. Anything that writes — delete item, boxhero - delete location — 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 Boxhero — 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 Boxhero to work with Luumen

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