Mirakl
E-commerceRun marketplace operations on Mirakl from AI agents: list and accept incoming orders, attach tracking and validate shipments, bulk-import offers, look up catalog products, and route seller message threads to your team.
What This Integration Enables
Selling on a Mirakl-powered marketplace means operating under someone else's clock: acceptance windows, shipping SLAs, and seller scorecards that remember every miss. This connector puts FlowRunner agents on that clock. Agents sweep incoming orders, verify stock, commit acceptance decisions, attach tracking, validate shipments, and keep offers synced in bulk, so the marketplace sees a seller who responds in minutes regardless of what the day looks like inside your operation. - Automate the order lifecycle: list, accept or refuse, track, and ship against Mirakl's state machine - Sync inventory and pricing with bulk offer imports keyed by shop SKU - Look up catalog products before creating offers against them - Monitor the seller inbox and route customer and operator message threads to the right owner - Feed order, offer, and product data into spreadsheets, dashboards, and fulfillment systems Refusing an order line is a commercial decision with a refund attached, which is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration draws its line. The same sweep discipline extends to the inbox: List Message Threads keeps customer and operator messages from aging past the marketplace's response expectations, routed to an owner like any other order exception instead of waiting for someone to remember the seller portal exists.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Storefront sales decrement marketplace stock
A new order fires from [Shopify](/integrations/shopify). The agent maps the sold SKUs to their Mirakl shop SKUs and calls Import Offers with updated quantities, so the marketplace stops advertising units your own storefront just sold. The overselling window shrinks from hours to minutes, and the refusals that overselling forces, each one a refund and a scorecard hit, stop happening.
Dispatch with the tracking already attached
The agent calls List Orders filtered to the SHIPPING state, hands each order to [ShipBob](/integrations/shipbob) for fulfillment, and waits on the tracking number. When it arrives, Update Tracking writes the carrier code, tracking number, and URL, then Ship Order validates the shipment so the buyer's notification goes out complete. No order is marked shipped without tracking, and no tracking arrives days after the box did.
The acceptance queue with a human where it counts
The sweep finds three new WAITING_ACCEPTANCE orders. Two are fully covered by stock: the agent accepts every line and logs them to [Google Sheets](/integrations/google-sheets). The third asks for five units of a SKU with three on hand. The agent posts the order detail to [Slack](/integrations/slack) with the shortfall named and the clock visible. The operations lead accepts three units and refuses two, knowing the refusal triggers a customer refund. The agent commits exactly that split with Accept or Refuse Order. Deadlines get met without the marketplace ever making the decision for you.
Human-in-Loop Highlight
Accept or Refuse Order is a one-way door with money on both sides. Accepting a line commits you to ship it on the marketplace's SLA; refusing a line cancels it and triggers a customer refund, with your seller metrics recording the outcome either way. And the WAITING_ACCEPTANCE state has a clock: decide in time or the marketplace decides for you. FlowRunner agents split this decision by risk. Lines that stock fully covers get accepted automatically, because there is no judgment in saying yes to an order you can fill. Shortfalls, suspect orders, and partial-fill tradeoffs pause with the full order detail from Get Order in front of the operations lead, who chooses the accept-refuse split per line. The agent commits it and archives the reasoning. The marketplace sees fast decisions; your P&L sees deliberate ones.
Agent Capabilities
9 actionsOrders
5- List Orders Retrieves orders via OR11 with filters for state, date windows, order IDs, channels, and free text. States span WAITING_ACCEPTANCE through SHIPPED, RECEIVED, CLOSED, REFUSED, and CANCELED. The sweep behind the whole lifecycle.
- Get Order Retrieves one order in full via OR12: customer, shipping detail, order lines with per-line states and SKUs, pricing, taxes, and promotions. The evidence step before every acceptance decision.
- Accept or Refuse Order Commits per-line accept or refuse decisions on a WAITING_ACCEPTANCE order via OR21. Accepting moves the order toward shipping; refusing cancels lines and triggers a customer refund. The operation this page's human gate exists for.
- Ship Order Validates the shipment via OR24, marking the order SHIPPED once physically dispatched. Requires the order to be in the SHIPPING state.
- Update Tracking Attaches carrier code, tracking number, and tracking URL via OR23. Set tracking before Ship Order so the buyer's shipping notification arrives complete.
Offers and Catalog
3- List Offers Retrieves the seller's offers via OF11 with SKU, price, quantity, state, and product association. The audit read before imports.
- Import Offers Creates or updates offers in bulk via OF21, each keyed by shop SKU with price, quantity, state, and discount fields, processed asynchronously with a returned import ID. The engine behind inventory and price sync.
- List Products Retrieves marketplace catalog products via P11 with identifiers, titles, category, and brand. The lookup before creating offers against catalog entries.
Inbox
1- List Message Threads Retrieves seller inbox threads via M11, each grouping the messages for an order or topic with subject, participants, and read state. The read behind message routing workflows.
Frequently Asked Questions
What can FlowRunner do with Mirakl?
FlowRunner agents can run List Orders, Get Order, and Accept or Refuse Order in Mirakl, plus 6 more actions.
Does connecting Mirakl to FlowRunner require OAuth?
No. Mirakl connects to FlowRunner with an API key, no OAuth flow required.
Can Mirakl trigger a FlowRunner workflow automatically?
Mirakl doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mirakl
$100 in credits. No card required. Connect in minutes.