FlowRunner
PricingContact
Theme
Start Free

Katana

ERP

Connect AI agents to Katana cloud manufacturing. Agents sync products and sales orders from your store, raise manufacturing orders when producible stock runs low, report live inventory and committed stock, and look up materials and customers.

11 actions API key available
Katana website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
The nightly inventory sweep runs against the production warehouse
List Inventory pulls in-stock, committed, and available quantities per variant with reorder points
Agent compares available stock against each variant's reorder point and open demand from List Sales Orders
List Manufacturing Orders confirms no open MO already covers the shortfall
Agent drafts a Create Manufacturing Order proposal with variant, quantity, and production location
The production planner reviews the proposed MO against material availability and the floor schedule, then approves or resizes it
Create Manufacturing Order raises the approved MO with the deadline attached
The reorder report and the new MO post to the operations channel

What This Integration Enables

Katana's model matches how small manufacturers actually think: products with variants, materials that compose them, sales orders that commit stock, and manufacturing orders that replenish it. The failure mode is never the model, it is the latency of humans ferrying data between the store, the spreadsheet, and the MRP. FlowRunner agents close that gap: they sync sales orders in from wherever demand arrives, watch inventory against reorder points, propose manufacturing orders when producible stock runs short, and publish the live picture to the tools the team already reads. The one discipline the connector enforces is Katana's own: order rows and MOs are keyed by variant ID, not product ID, so agents resolve variants through List Products before writing anything. That is exactly the kind of bookkeeping that should never have been a human job. - Storefront and CRM demand becomes Katana sales orders without re-keying - Inventory sweeps report in-stock, committed, and available per variant and location - Shortfalls become proposed manufacturing orders, sized against demand and existing open MOs - Product and customer catalogs stay queryable for every downstream automation - Fulfilled orders flow onward to invoicing without a manual handoff Production capacity is finite and materials are real, which is why the moment an agent proposes to consume them is precisely where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits.

Without FlowRunner

Reordering runs on walk-arounds Someone notices a bin looks low, and the gap between noticing and producing is measured in stockouts
The store and the factory disagree Shopify sells what Katana says is committed, because order entry happens twice by hand
Committed stock is invisible In-stock numbers look healthy while open sales orders have already claimed most of it

With FlowRunner

Shortfalls surface themselves Agents sweep inventory nightly, net available stock against reorder points and demand, and propose the MO
Orders flow in once Storefront orders become Katana sales orders automatically, with lines mapped to the right variant IDs
Available is the number that matters Reports show in-stock, committed, and available side by side, so promises match what production can keep

Use Case Scenarios

A Shopify order becomes production demand in one pass

An order lands in [Shopify](/integrations/shopify). The agent resolves each line to its Katana variant ID via List Products, matches the buyer with List Customers, and calls Create Sales Order with delivery date and fulfilment location. Then it checks List Inventory: if available stock covers the order, done. If a producible variant falls short, the agent drafts a manufacturing order proposal for the planner. The storefront, the MRP, and the production queue now describe the same reality, and nobody typed an order twice.

The reorder report that arrives before the stockout

Every night the agent walks List Inventory page by page, flags every variant where available quantity sits below its reorder point, and cross-references List Manufacturing Orders so variants already being produced are not flagged twice. The result lands as rows in [Google Sheets](/integrations/google-sheets) and a morning summary in [Slack](/integrations/slack): what is short, what is committed, what is already in production, and what needs a decision. The planner starts the day with the exceptions, not with the counting.

Fulfilled orders bill themselves

On a schedule, the agent pulls List Sales Orders filtered to fulfilled status, retrieves each with Get Sales Order for full line detail, and creates the corresponding invoice in [QuickBooks Online](/integrations/quickbooks) with quantities, prices, and tax carried across. New products created in Katana propagate to the accounting item list the same way. Finance stops chasing operations for what shipped, because the workflow tells them, with the order ID attached for the audit trail.

Human-in-Loop Highlight

Create Manufacturing Order spends things that do not come back: raw materials get consumed, machine time gets scheduled, and labor gets committed to producing the planned quantity. An agent that misreads demand, a duplicate order the sweep missed, an inflated quantity, turns directly into cost sitting on a shelf as unsold finished goods. So FlowRunner agents never raise an MO unprompted. The agent does the analysis: current stock, committed quantities, open MOs, incoming demand, and presents a sized proposal. The production planner, who knows the floor schedule and the material deliveries the API cannot see, approves, resizes, or rejects it. Only then does Create Manufacturing Order execute. The sweep runs at machine speed every night; the decision to consume materials stays with the person accountable for the production plan.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

11 actions

Products

3
  • List Products Retrieves a paginated list of products from Katana. Products are sellable, producible, or purchasable items with one or more variants. Supports filtering by name, unit of measure, category, and capability flags (sellable/producible/purchasable). Each product includes its variants with SKUs and pricing. Use limit and page to page through large catalogs.
  • Get Product Retrieves a single product by its numeric Katana ID, including all of its variants with SKUs, sales and purchase prices, barcodes, and configuration attributes. Use List Products to discover product IDs.
  • Create Product Creates a new product in Katana. A product requires a name and at least one variant (each variant needs a unique SKU and may carry sales/purchase prices). Optional flags control whether the product is sellable, producible, or purchasable, and you can set the unit of measure and category. Returns the created product with its generated ID and variant IDs.

Inventory

1
  • List Inventory Retrieves current inventory levels per variant and location. Each row reports in-stock, committed, and available quantities plus the average cost and reorder point for a variant at a location. Filter by location to see stock at a specific warehouse. Use limit and page to page through results.

Sales Orders

3
  • List Sales Orders Retrieves a paginated list of sales orders. Supports filtering by order number, customer, location, and production status. Each order includes its rows (line items), customer reference, delivery date, and fulfilment status. Use limit and page to page through results.
  • Get Sales Order Retrieves a single sales order by its numeric Katana ID, including all line items (rows) with variant, quantity, price, and tax, plus the customer, delivery date, addresses, and fulfilment status. Use List Sales Orders to discover order IDs.
  • Create Sales Order Creates a new sales order for a customer. Requires a customer ID and at least one order row (each row needs a variant ID and quantity). Optionally set an order number (auto-generated if omitted), delivery date, fulfilment location, and currency. Returns the created sales order with its generated ID and computed row totals.

Manufacturing Orders

2
  • List Manufacturing Orders Retrieves a paginated list of manufacturing orders (MOs). Each MO tracks the production of a product variant at a location, with planned and actual quantities and a production status. Supports filtering by order number, status, and location, and by whether the MO is linked to a sales order. Use limit and page to page through results.
  • Create Manufacturing Order Creates a new manufacturing order to produce a product variant at a location. Requires the variant ID, the planned quantity to produce, and the production location ID. Optionally set an order number, creation date, and production deadline. Note that Katana identifies the item to produce by variant ID (from a product's variants), not by product ID. Returns the created MO with its generated ID.

Materials

1
  • List Materials Retrieves a paginated list of materials (raw components used in production). Supports filtering by name, unit of measure, category, and default supplier. Each material includes its variants with SKUs and purchase pricing. Use limit and page to page through results.

Customers

1
  • List Customers Retrieves a paginated list of customers. Supports filtering by name, company, email, and reference ID. Each customer includes contact details, default currency, and any stored addresses. Use limit and page to page through results, and use customer IDs when creating sales orders.

Frequently Asked Questions

What can FlowRunner do with Katana?

FlowRunner agents can run List Products, Get Product, and Create Product in Katana, plus 8 more actions.

Does connecting Katana to FlowRunner require OAuth?

No. Katana connects to FlowRunner with an API key, no OAuth flow required.

Can Katana trigger a FlowRunner workflow automatically?

Katana doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Katana

$100 in credits. No card required. Connect in minutes.