Magento 2

Manage Magento 2 and Adobe Commerce products, orders, customers, categories, and sales documents from automated flows. Agents sync catalog and stock, invoice and ship orders, keep customer records in step, and report on sales activity through the Magento REST API.

28 actions available

Scheduled run calls List Orders for orders placed since the last poll

Agent reads the line items, customer email, and totals for each new order

Agent validates stock availability per SKU with Get Stock Item

Agent checks each order against fraud signals and a high-value threshold

Agent calls Create Invoice for Order and Create Shipment for clean orders

Operations channel gets the batch summary and the list of flagged orders

Orders flagged for cancellation get routed to ops for a keep-or-cancel decision

What This Integration Enables

The Magento 2 integration gives agents read and write access across products (create, update, delete, and stock control), orders (list and get, invoice, ship, comment, hold, unhold, and cancel), customers (full lifecycle), the category tree and category-to-product assignments, and sales documents (invoices, shipments, and credit memos). List endpoints accept a simple Filters array that maps to Magento's searchCriteria, so agents narrow results by status, email, date range, or name without hand-building the verbose query format. The connector covers the operational surface a fulfillment or reporting flow needs; the surrounding flow decides what runs unattended and what stops for a person.

Without FlowRunner

Manual order polling Someone exports the day's orders and works them one at a time from a spreadsheet

Fulfillment by hand Invoicing and shipping each order means clicking through the admin panel order by order

Cancellations with no record Cancel decisions get made verbally and keyed into Magento with no consistent trail of who approved them

With FlowRunner

Orders worked on a schedule Each run pulls new orders, validates stock, and invoices and ships the clean ones automatically

Fulfillment in the flow Invoices and shipments are created programmatically as orders qualify

Cancellations with approval on record Every cancel is proposed with full context and executed only after a named approver signs off

Use Case Scenarios

Scheduled Order Fulfillment

On a schedule, the agent calls List Orders filtered to a pending status and a created_at range covering the window since the last run. For each order it checks stock with Get Stock Item, then for a clean order it calls Create Invoice for Order and Create Shipment, and hands the tracking number to [ShipBob](/integrations/shipbob/) or emails the customer a confirmation. Orders that fail the stock check or trip a review rule are held with Hold Order and posted to the operations channel for a human to work.

Catalog and Stock Sync

An external system of record owns pricing and on-hand counts. The agent reads the source feed, looks up each product with Get Product by SKU, and calls Update Product and Update Stock so the storefront reflects the source of truth. When a SKU drops below its reorder point, the agent posts a note to the buying channel so the dip is visible when it happens rather than at the next stockout.

Sales Reporting Across Documents

Finance needs a weekly view of what actually happened. The agent queries List Orders, List Invoices, List Shipments, and List Credit Memos with created_at filters for the week, reconciles them per order, and posts the summary to a reporting channel or appends it to a shared sheet. The credit memos surface the refunds, so the report shows net sales without anyone exporting four separate CSVs.

Human-in-Loop Highlight

Cancelling an order is a decision a store cannot cleanly take back, so the agent proposes the cancellation and stops. When an exception flow reaches a candidate for cancellation, whether a failed fraud check, an out-of-stock backorder, or a customer request, the agent gathers the order, the customer, the totals, and the reason, then posts to the operations channel: "Cancel requested for order [number], customer [name], total $[amount]. Reason: [reason]. Approve to cancel?" The agent has assembled the case; the named approver owns the keep-or-cancel call, and only after they approve does the agent call Cancel Order and notify the customer. This is [human-in-the-loop](/concepts/human-in-the-loop/): the agent pauses on its own, assembles the context and the choices, routes to the approver through the channel they already use, such as [Slack](/integrations/slack/), and resumes the instant they respond.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

17 actions

Products

List Products / Get Product Search the catalog with searchCriteria filters, or pull one product by SKU with price, status, visibility, and custom attributes. Used to find products before acting on them or to feed catalog data downstream.
Create Product / Update Product / Delete Product Full product lifecycle. Used to onboard SKUs from a supplier feed, adjust pricing or attributes, and retire end-of-life items.
Get Stock Item / Update Stock Read a product's stock item (quantity, stock status, and the item_id needed to update it), then set quantity and in-stock status. Used to sync on-hand counts from a WMS or reconcile after a delivery.

Orders

List Orders / Get Order Search orders with searchCriteria filters (status, customer_email, created_at), or pull one order with line items, totals, and addresses. Used to work new orders and to reconcile.
Create Invoice for Order Creates an invoice for an order, optionally capturing payment and notifying the customer. Used to advance an order once it qualifies for fulfillment.
Create Shipment Creates a shipment for an order, optionally with items and tracking numbers, and can notify the customer. Used to book fulfillment and share tracking.
Add Order Comment Adds a comment to an order's status history, optionally changing status and notifying the customer. Used to record fulfillment updates and customer communication.
Cancel Order Cancels an order in a cancelable state. This is the irreversible step a human-in-loop approval gate sits in front of, so a person owns the keep-or-cancel call.
Hold Order / Unhold Order Places an order on hold so it cannot be invoiced or shipped, then releases it. Used to pause an order for review and resume it once cleared.

Customers

List Customers / Get Customer Search customers with searchCriteria filters, or pull one customer with group, store, and address book. Used to look up buyers or mirror records into a CRM.
Create Customer / Update Customer / Delete Customer Full customer lifecycle. Used to keep customer records in step with the CRM and marketing platform.

Sales Documents

List Invoices / Get Invoice Search invoices with searchCriteria filters, or pull one invoice with line items and totals. Used in reconciliation and finance reporting.
List Shipments Retrieves shipments with searchCriteria filters. Used to report on fulfillment progress.
List Credit Memos Retrieves credit memos (refunds) with searchCriteria filters. Used to surface refunds in net-sales reporting.

Start building with Magento 2

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

Start Building Free Talk to us