Google Merchant Center
E-commerceManage your Google Shopping product feed from AI agent workflows. Agents insert, list, and delete Merchant Center products, audit per-product approval status and data quality issues, and review data feeds and orders through the Content API for Shopping.
What This Integration Enables
Your Merchant Center feed is a second storefront, the one Google's shoppers see, and it fails silently: a disapproved product does not error, it just stops appearing. This connector puts FlowRunner agents on both halves of the problem. On the supply side, agents insert and update products through the Content API so the feed tracks the store. On the audit side, they sweep approval statuses and item-level issues daily, turning the Diagnostics tab into a routed worklist with an owner. - Sync a product catalog into Google Shopping from a store or spreadsheet, upserted by offer ID - Audit which products are approved to serve, per destination, on a schedule - Surface item-level data quality issues, missing GTINs, policy violations, with the affected product - Remove discontinued products from Shopping ads and free listings deliberately - Review configured data feeds and Merchant Center orders inside automated workflows Removal is the sharp edge: Delete Product cannot be undone, so FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration keeps a merchandiser between the audit and the delete. The discipline the connector enforces is verification. Insert Product returning success means Google accepted the upload, not that shoppers will see the item; approval happens later, per destination, and only Get Product Status tells the truth. Building that second check into every publish flow is the difference between a feed you believe is live and one you know is.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The catalog sheet that publishes itself
The merchandising team maintains the product catalog in [Google Sheets](/integrations/google-sheets). On every scheduled run, the agent reads changed rows and calls Insert Product for each, building the REST ID from channel, language, country, and offer ID so existing products update in place. Price changes propagate the same day they are decided, and the spreadsheet the team already trusts becomes the feed's source of truth.
New in the store, live on Google, verified approved
A new product fires from [Shopify](/integrations/shopify). The agent maps it into Insert Product, waits out processing, then calls Get Product Status to confirm the item is actually approved to serve rather than assuming the upload worked. Anything disapproved posts to [Slack](/integrations/slack) with the item-level issue quoted, so the listing gets fixed while the product launch still has momentum.
The daily disapproval sweep
Every morning, List Product Statuses pages through the full account. The agent diffs against yesterday's state, groups new issues by type, missing GTIN here, price mismatch there, and posts a worklist to the merchandising channel with each affected product resolved via Get Product. Items the team marks as discontinued go to a confirmation step, then Delete Product removes them from ads and free listings. The feed stays clean because cleaning it is nobody's manual job anymore.
Human-in-Loop Highlight
Calling Delete Product removes the catalog entry, its approval history, and its serving eligibility in one irreversible stroke, and the action's own contract says there is no undo. The trap is that deletion looks like the obvious fix for a disapproved product, when the right fix is usually a data correction, and the wrong delete takes a revenue-generating listing off Google entirely. So FlowRunner agents never delete from an audit. The disapproval sweep proposes; a merchandiser disposes. Each candidate for removal arrives with its status detail from Get Product Status and its full record from Get Product, and only an explicit confirmation runs Delete Product. Fixing a feed is automation. Shrinking a storefront is a decision.
Agent Capabilities
9 actionsProducts
4- List Products Lists the account's products with REST ID, offer ID, title, price, and availability, paginated by page token. The inventory read behind feed audits and syncs.
- Get Product Retrieves a single product by its full REST ID with every feed attribute: title, description, link, image, price, condition, channel. The detail read before fixes and removals.
- Insert Product Uploads a product, or updates it when the channel, language, country, and offer ID match an existing item. Price is a value plus currency; availability and condition accept friendly labels. The workhorse write behind catalog sync.
- Delete Product Permanently removes a product by its full REST ID, stopping it from serving in Shopping ads and free listings. Cannot be undone. The operation this page's human gate exists for.
Statuses and Diagnostics
2- List Product Statuses Reports every product's approval state per destination and its item-level data quality issues, paginated. The engine behind the daily disapproval sweep.
- Get Product Status Retrieves one product's approval state and issues by REST ID. The verification step after every insert, and the evidence attached to every removal request.
Feeds, Orders, and Account
3- List Datafeeds Lists the account's configured data feeds with ID, name, file and fetch settings, and target destinations. The read that shows how product data currently enters Merchant Center.
- List Orders Lists Merchant Center orders with status, line items, customer, and shipping detail, filterable by status and acknowledgement state. Requires orders to be enabled on the account.
- Get Account Retrieves account information, including sub-accounts under a multi-client account: name, website URL, users, and business information. The configuration check for multi-account setups.
Frequently Asked Questions
What can FlowRunner do with Google Merchant Center?
FlowRunner agents can run List Products, Get Product, and Insert Product in Google Merchant Center, plus 6 more actions.
Does connecting Google Merchant Center to FlowRunner require OAuth?
Yes. Google Merchant Center connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Google Merchant Center trigger a FlowRunner workflow automatically?
Google Merchant Center doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Google Merchant Center
$100 in credits. No card required. Connect in minutes.