Connect Notion to Boxhero
When something happens in Notion, Notis takes the next step in Boxhero. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Boxhero
View exampleCheck inventory for new product records
When a product record is added to Notion, look up the matching Boxhero item and report its current inventory details.
View examplePull item details for stock reviews
When a Notion stock review page changes, retrieve the referenced Boxhero item's full details for a concise review summary.
View exampleReview location activity from restock notes
When a restock note is created, retrieve Boxhero transactions for the relevant location and summarize recent in, out, move, and adjustment activity.
View exampleAnswer inventory questions with transaction context
When a teammate comments on an inventory page, retrieve a high-level Boxhero transaction overview to give the discussion useful context.
View exampleCheck Boxhero when a supplier is added
When a supplier record is added to Notion, list matching Boxhero partners to surface existing supplier details and avoid repeat research.
View exampleResolve warehouse locations from planning updates
When a Notion warehouse planning page changes, list Boxhero locations so Notis can surface the relevant location details for the plan.
View exampleCheck item attributes when catalog guidance changes
When a Notion catalog guide is edited, retrieve Boxhero's defined item attributes and summarize which fields the guide should account for.
View exampleCheck team members for new inventory ownership notes
When a Notion inventory ownership note is created, retrieve the Boxhero team member list to help confirm the operational contact.
View exampleCheck linked Boxhero team before operational setup
When a new operations page is created in Notion, retrieve linked Boxhero team information so the team context is clear before work begins.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Boxhero
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.