VTEX
E-commerceConnect AI agents to your VTEX commerce cloud. Agents list and inspect orders, look up products, SKUs, inventory, and pricing, and push price updates directly through the VTEX APIs.
What This Integration Enables
VTEX runs commerce at a scale where the catalog is not a list, it is a system of record with four subsystems: OMS for orders, Catalog for products and SKUs, Logistics for per-warehouse inventory, and Pricing for the numbers customers actually pay. This connector gives FlowRunner agents structured access to all four, reads across everything and one precise, high-consequence write: pushing base price updates. That shape makes it the working layer for pricing operations, order monitoring, and stock intelligence on VTEX stores. - Monitor orders from the OMS by status and free-text search, with full detail per order - Walk the catalog from product IDs to SKUs to specifications, resolving any item programmatically - Check per-warehouse stock, including reserved quantities, before promising delivery or reordering - Read complete pricing records: base, cost, markup, list, and computed sell price - Push base-price updates through a governed, reviewed workflow Pricing is the write that touches every customer at once, so it is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration stands. The read-heavy shape is deliberate leverage. VTEX's subsystems each answer one question well, and most operational pain is stitching those answers together: the order needs the SKU, the SKU needs the warehouse position, the pricing decision needs cost and margin context. An agent walks those joins in seconds and delivers the composed answer where the team works, which is most of what an operations dashboard ever promised and rarely delivered.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order digest with exceptions surfaced
Every hour, List Orders sweeps the OMS with a status filter, and Get Order pulls full detail for anything new or changed. A digest posts to [Slack](/integrations/slack): counts by status, revenue, and the exceptions called out, payment pending too long, fulfillment stalled. The team watches one channel instead of a saved OMS filter, and stuck orders get attention while the customer is still patient.
The live stock-and-price sheet
Nightly, the agent walks List Product and SKU IDs, calling Get Inventory and Get Price per SKU, and rebuilds a report in [Google Sheets](/integrations/google-sheets): stock per warehouse with reservations, current sell price, cost, and margin. Merchandising reads warehouse reality every morning without asking anyone, and reorder conversations start from the same numbers the platform holds.
Post-purchase marketing from order truth
When Get Order returns a completed order, the agent syncs the client profile and purchase into [Klaviyo](/integrations/klaviyo), profile updated, purchase event recorded, feeding the post-purchase sequence: care instructions, replenishment timing, the considered cross-sell. Campaign logic runs on what customers actually bought, priced as they actually paid, rather than a stale export of both.
Human-in-Loop Highlight
Update Price writes the base price a live storefront charges, and it takes its value in the store's minor currency unit: 15990 means 159.90. That convention is exactly where automation bites, one missing conversion and the price lands at a hundredth of its intent, live, on every trade policy reading the base price, until someone notices. Wrong prices honored cost margin; wrong prices retracted cost trust. So in FlowRunner, no Update Price call executes straight from computation. The agent assembles the change set with Get Price context, current value, proposed value, margin against cost, formats every figure in plain currency alongside the raw minor units, and flags anything below cost or beyond the expected band. The pricing owner approves the set, and the agent writes it and archives the before-and-after. The arithmetic runs at machine speed. The number the customer sees was approved by a person who saw it the way the customer would.
Agent Capabilities
8 actionsOrders
2- List Orders Lists OMS orders with free-text search across order IDs and customer data, status filtering, and paging, returning summaries plus stats metadata. The sweep behind order monitoring.
- Get Order Retrieves one order in full by ID: items, client profile, shipping and invoice data, payments, totals, and current status. The detail step behind digests, support, and marketing sync.
Catalog
3- Get Product Retrieves a catalog product by internal ID: name, brand, category, description, and active and visible flags. Products group SKUs; use Get SKU for item-level detail.
- List Product and SKU IDs Lists product IDs mapped to their SKU IDs with paging and a range descriptor. The walking read that keys every per-SKU workflow.
- Get SKU Retrieves full SKU detail: name, product association, EAN and reference codes, dimensions, weight, images, and specification values. The item-level read for catalog and fulfillment flows.
Inventory and Pricing
3- Get Inventory Retrieves a SKU's stock across all warehouses from Logistics: per-warehouse totals, reserved quantities, and unlimited-stock flags. The check before promises and reorders.
- Get Price Retrieves a SKU's pricing record: base price, cost, markup, list price, computed sell price, and any fixed per-trade-policy or scheduled prices, in minor currency units. The context read before every price change.
- Update Price Creates or updates a SKU's base price, with optional cost, markup, and list price, in minor currency units. The operation this page's human gate exists for.
Frequently Asked Questions
What can FlowRunner do with VTEX?
FlowRunner agents can run List Orders, Get Order, and Get Product in VTEX, plus 5 more actions.
Does connecting VTEX to FlowRunner require OAuth?
No. VTEX connects to FlowRunner with an API key, no OAuth flow required.
Can VTEX trigger a FlowRunner workflow automatically?
VTEX doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with VTEX
$100 in credits. No card required. Connect in minutes.