hivein for Botble
Your Botble store's catalogue, orders, pages and SEO, changed through Botble's own rules rather than raw SQL.
A login for the store's MySQL or Postgres database. Before a single tool is generated, hivein checks that the tables are Botble's own: slugs, settings, meta boxes and pages.
- Edit the catalogue the way Botble does
- Move orders through their states
- Promotions that ask first
- Pages, blog and menus
- Settings without secrets
Your Botble, as actions the copilot can take.
Edit the catalogue the way Botble does
Products, categories, collections, tags and brands are written together with their URL slug, SEO title and description, and translations, so a new product arrives with its storefront page, not just a database row. Variants are added, changed or removed in one call.
Move orders through their states
Confirm, complete or cancel an order with Botble's own bookkeeping: order history, invoice, restocking and coupon reversal. Orders are never created or deleted from the conversation.
Promotions that ask first
Discounts, flash sales, shipping, taxes and currencies are writes that wait for your approval by default, so a price change is in front of you before it reaches the storefront.
Pages, blog and menus
Pages, blog posts with their categories and tags, galleries and menus are all reachable. Changing a slug moves the live URL and Botble adds no redirect, so that is said before it happens.
Settings without secrets
Store settings are updated by key, the home page set, and payment methods switched on or off. Any setting whose key names a secret, password, token or API key is never read or written.
Botble Sidekick arrives with these.
Written in plain language, not configuration — change a sentence and the behaviour changes with it.
Writes need receipts
A write is reported from what the tool returned, its ids and affected rows, never from what was intended.
Bulk-write care
A change that touches more than a handful of rows shows the exact rows and is confirmed against that list.
Storefront language
The locales that exist are checked first, then the right translation rows are updated, or the untouched locales are named.
It reads your Botble 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.
“Which products are out of stock but still published?”
“How many orders were cancelled this month, and what were they worth?”
“Set up a 15% flash sale on the winter collection for this weekend”
“Which product pages are missing an SEO description?”
Writes to Botble wait for you.
The same three guardrails hold on every template. They are attached to the action itself, so they hold on every path. Watch the replay →
- 01
The plan is held
A plan that writes to a real system stops before it starts. You see the goal, the risk and every step, then confirm or reject.
- 02
Each write asks first
A tool marked ask-first shows the exact call with its values. Confirm it, edit the values, or reject it. Nothing runs until you decide.
- 03
A rejection is an instruction
Pick a reason and add a line. The copilot re-plans with what you told it instead of guessing.
Botble questions.
Does it need a Botble plugin?
No. hivein connects to the store's database, confirms the tables are Botble's, and generates its tools from what it finds there.
Can it delete products?
Deletes are permanent in Botble, so every delete asks first, and a delete is refused while the store still depends on the row. A product that appears on customer orders is set to draft instead.
What does the Botble Sidekick template add?
The tools for catalogue, orders, pages and settings, sixteen store skills, and guidelines that make it report what a write actually returned, confirm bulk changes against the exact rows, and update the right translations.
More templates like this one.
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
Magento
Open sourceOrders, quotes and catalogue attributes across every website and store view of a single Magento install.
In developmentSee the plan → — Magento
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 → — ShopwareConnect Botble. Get a copilot this afternoon.
No card, no agent configuration, no prompt to write. Sign in and approve the actions it may take.