BoxHero is a cloud-based inventory management solution designed for small to medium-sized businesses, offering real-time updates, barcode scanning, team collaboration, and analytics.
BoxHero is a cloud-based inventory management solution designed for small to medium-sized businesses, offering real-time updates, barcode scanning, team collaboration, and analytics. On Nagent, Boxhero is exposed as a fully-configurable product management integration that any agent can call — 14 actions, and API key authentication. No code is required to wire Boxhero into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Boxhero to automate the kinds of tasks product management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Boxhero into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Boxhero, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BOXHERO_DELETE_ITEMTool to delete a specific item (barcode) by its ID. Use when you need to remove an item from the inventory.
Input parameters
The ID of the item to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_DELETE_LOCATIONTool to delete a specific warehouse location by its ID. Use when you need to remove a location from the system.
Input parameters
The ID of the location to be deleted
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_GET_ITEMTool to retrieve a specific item (barcode) by ID. Use when you need detailed information about a single item including its attributes, pricing, and inventory quantities.
Input parameters
The id of the item to be queried
The ids of the locations to be used for quantity calculation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_GET_ITEM_ATTRIBUTETool to retrieve a specific item attribute by ID. Use when you need to get detailed information about an item attribute specification.
Input parameters
The unique identifier of the item attribute to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_GET_LOCATIONTool to retrieve a specific location by ID. Use when you need detailed information about a particular warehouse location including its name, quantity, and notes.
Input parameters
The id of the location to be queried
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_GET_MEMBERTool to retrieve a specific team member by ID. Use when you need to get details about a particular member.
Input parameters
Unique identifier of the team member to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_GET_TEAM_INFOTool to get information about the linked team and its mode. Use when you need to retrieve the currently linked team details.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_BASIC_TRANSACTIONSTool to list basic inventory transactions. Use when you need a high-level overview of in/out/move transactions.
Input parameters
Maximum number of transactions to return per request (default 100)
Cursor token for fetching the next page of results
Filter transactions by location ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_ITEM_ATTRIBUTESTool to retrieve the list of item attribute specifications used within the team. Use when you need to understand what custom attributes are defined for items.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_ITEMSTool to list items. Use when fetching products with optional location filters and pagination.
Input parameters
Maximum number of items to return in one page.
Cursor token for fetching the next page of results.
Filter items by one or more location IDs. Repeatable parameter.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_LOCATIONSTool to list warehouse locations. Use when you need valid warehouse_id values for filtering transactions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_LOCATION_TRANSACTIONSTool to retrieve the list of transactions in location mode. Use when you need to fetch transaction history with location-based details including in/out/move/adjust operations.
Input parameters
Transaction type enum for filtering location transactions.
Maximum number of items to return in a single request (default 100, max 100)
Cursor pointing to a specific spot in the items, allowing clients to request the next set of items
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_MEMBERSTool to retrieve the list of team members. Use when you need to get all members in the team with their roles.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOXHERO_LIST_PARTNERSTool to list partners (suppliers and customers). Use when retrieving partner information with optional type filtering and pagination.
Input parameters
Partner type enumeration.
The maximum number of items to be returned in a single request (default 100)
Points to a specific spot in the items, allowing clients to request the next set of items
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 83 agents privately built on Nagent that already use Boxhero.
Build on Nagent
Connect Boxhero to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Boxhero, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Boxhero is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Boxhero is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Boxhero steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Boxhero event fires, the agent kicks off automatically.
Every Boxhero action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Boxhero ships with 14 pre-built product management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Boxhero together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Boxhero-based workflows tailored to your business.