hivein for Magento
Orders, quotes and catalogue attributes across every website and store view of a single Magento install.
Through Magento's REST API using an admin integration access token, limited to the ACL resources that integration is granted.
- Search orders with searchCriteria filter groups
- Read the catalogue as EAV, not as a flat table
- Follow the quote-to-credit-memo chain
- Check stock across inventory sources
- Audit cart price rules and coupons
What the Magento connector will do.
Search orders with searchCriteria filter groups
Magento's REST search builds a query from filter groups, ANDed together from groups of OR conditions, so an order question will filter on status, store, grand total or date range and page through what comes back.
Read the catalogue as EAV, not as a flat table
Products carry EAV attributes grouped into attribute sets, and configurable, bundle and grouped types point at child SKUs. Values will be read at the store-view scope they were actually set on.
Follow the quote-to-credit-memo chain
A Magento sale moves from quote to order to invoice to shipment to credit memo, each its own REST resource. Joining them will separate what was ordered from what was billed, shipped and refunded.
Check stock across inventory sources
Multi-Source Inventory keeps a source item per SKU per source alongside a salable quantity computed per stock. Both will be read, rather than one number that hides which warehouse is empty.
Audit cart price rules and coupons
Cart price rules and the coupon codes generated from them are exposed over REST, including the websites, customer groups and conditions each rule applies to.
It will read your Magento data model, not a generic one.
The schema is read first, so a question that spans two of these is one question, not two lookups.
“Show me the store views that raised the most credit memos last month”
“Which inventory sources have run out for SKUs that are still salable overall”
“Which product attributes carry a store-view value that differs from the default”
“How many active cart price rules have produced no order this quarter”
Magento questions.
Will this work with both Magento Open Source and Adobe Commerce?
The integration is being built on REST resources that exist in both, so orders, catalogue, customers and inventory behave the same either way. Adobe Commerce-only features such as customer segments and B2B company accounts are outside the planned scope.
How will a multi-website install be handled?
Magento returns most records with a website, store or store-view scope attached, and that scope will be carried into the answer rather than dropped on the way. A question can also name a single store view.
What credentials will it need?
An admin integration with an access token, granted only the ACL resources the assistant needs. Magento enforces those resources server-side, so anything outside the grant is simply not reachable.
More templates like this one.
BtBotble
Closed sourceYour Botble store's catalogue, orders, pages and SEO, changed through Botble's own rules rather than raw SQL.
Tools from your schemaOpen template → — Botble
Shopify
Closed sourceAsk about orders, stock and customers in your store; catalogue and fulfilment edits wait for confirmation.
32 actionsOpen template → — ShopifyWcWooCommerce
Open sourceAnswer order, stock and refund questions against your WooCommerce store's own data.
TemplateOpen template → — WooCommerce
Medusa
Open sourceAsk your Medusa backend about orders, stock and price lists without writing another admin API call.
In developmentSee the plan → — MedusaOpOpenCart
Open sourceSales, catalogue and customer answers read straight from the OpenCart database, however modified it is.
In developmentSee the plan → — OpenCart
PrestaShop
Open sourceOrders, combinations, carts and cart rules from a PrestaShop shop, read through its built-in Webservice API.
In developmentSee the plan → — PrestaShopSaSaleor
Open sourceOne place to ask about Saleor orders, channel pricing and warehouse stock without writing GraphQL.
In developmentSee the plan → — Saleor
Shopware
Open sourceSales-channel-scoped answers about orders, rules and Flow Builder in Shopware 6, through the Admin API.
In developmentSee the plan → — ShopwareWant Magento next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.