Get Boxhero location details for warehouse issues
Log a warehouse issue in Notion and have Notis check the relevant Boxhero location details for a more informed follow-up.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get Location
Tool to retrieve a specific location by ID. Use when you need detailed information about a particular warehouse location including its name, quantity, and notes.
Why this helps
Warehouse issues often need a location check before anyone can decide what to investigate next.
- Add location context to the issue while it is being triaged.
- Reduce the extra search needed to understand a warehouse reference.
- Help the next owner start with clearer information.
Setup
Build it in a few focused steps.
- 1Connect Notion and Boxhero to Notis once through the portal.
- 2Create an automation in the portal or tell Notis how to handle new warehouse issues.
- 3Write one plain-language instruction asking Notis to retrieve details for the Boxhero location named in the issue.
- 4Select the Notion New Page trigger and choose a channel for run reports.
- 5Test with one real issue referencing an existing Boxhero location.
Questions about this workflow
What location information can be returned?
The Get Location action retrieves details for a specific location, including its name, quantity, and notes.
Does this resolve the warehouse issue?
It gathers location context for triage. A person still decides and carries out the next step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Boxhero. A trigger fires from one place; an action lands in another.
Notion triggers
Boxhero actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Item
Tool to delete a specific item (barcode) by its ID. Use when you need to remove an item from the inventory.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
BoxHero - Delete Location
Tool to delete a specific warehouse location by its ID. Use when you need to remove a location from the system.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Item
Tool 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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get Item Attribute
Tool to retrieve a specific item attribute by ID. Use when you need to get detailed information about an item attribute specification.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Location
Tool to retrieve a specific location by ID. Use when you need detailed information about a particular warehouse location including its name, quantity, and notes.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get Member
Tool to retrieve a specific team member by ID. Use when you need to get details about a particular member.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Get Linked Team Info
Tool to get information about the linked team and its mode. Use when you need to retrieve the currently linked team details.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
BoxHero - List Basic Transactions
Tool to list basic inventory transactions. Use when you need a high-level overview of in/out/move transactions.
Connect any two apps with Notis in the middle.
Notion and Boxhero, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Boxhero.