Facebook Catalogs
E-commerceManage the Meta product catalogs behind Facebook and Instagram Shops and dynamic ads. Agents sync external product feeds with batch operations, add and update individual products with price and availability, and browse catalogs and product sets through the Graph API.
What This Integration Enables
A Meta product catalog is not an internal database. It is the version of your store that Facebook and Instagram show to the public, and dynamic ads spend real budget promoting whatever it says. That makes catalog accuracy a money problem: a stale availability flag buys clicks for a product you cannot ship, and a price entered wrong in minor units, 199 instead of 1999, is a public mispricing amplified by ad delivery. FlowRunner agents treat the catalog as the last mile of commerce data: they sync it from the systems that actually know the truth, and they treat bulk writes with the suspicion bulk writes deserve. The connector speaks the Graph API's own dialect: retailer_id as your stable SKU key, prices in minor units with ISO currency codes, and Batch Items as the efficient path for anything beyond a single product. - Sync external product feeds into Meta catalogs with batched create, update, and delete operations - Add individual products with price, availability, condition, and images when they launch - Keep price and availability current so Shops and dynamic ads reflect reality - Resolve catalogs and browse product sets to understand what powers which ads - Audit catalog state on a schedule and report drift before customers find it
Without FlowRunner
With FlowRunner
Use Case Scenarios
The storefront-to-Shop pipeline
New products go live in [Shopify](/integrations/shopify). The agent maps each one to the catalog's field model, prices converted to minor units, availability set from inventory, and calls Batch Items with UPDATE operations keyed by SKU. Products appear in the Facebook and Instagram Shop without anyone re-entering them in Commerce Manager, and the same keys mean tomorrow's price change updates rather than duplicates.
The stock-out that stops spending money
Inventory hits zero for a SKU in the warehouse system. Within the next sync cycle, Batch Items flips that product's availability to out of stock, pulling it from dynamic ad delivery. When stock returns, the flag flips back. The merchandising team stops discovering stock-outs through ad comments, and ad budget stops flowing to products that bounce at checkout.
The weekly catalog audit
Every Monday, List Catalogs resolves the business's catalogs, and List Products pages through each one. The agent cross-checks price and availability against the commerce platform, writes the mismatches to [Google Sheets](/integrations/google-sheets), and posts a summary to [Slack](/integrations/slack): products missing images, prices that disagree with the store, items live in the catalog but retired in the ERP. List Product Sets adds which ad-powering sets each offender belongs to, so fixes get prioritized by blast radius.
Human-in-Loop Highlight
Batch Items with the DELETE method removes products from the catalog in bulk, and Delete Product is explicitly permanent. What sits downstream is the reason to pause: the catalog powers live Shops and running ad campaigns, so a bad batch does not fail quietly in a database, it empties a public storefront and starves the dynamic ads that were selling. The classic failure is a truncated feed export: the source sends 200 rows instead of 4,000, and a naive sync deletes 95 percent of the catalog. FlowRunner workflows compute the diff first and put a rule in front of the apply: deletions above a small fraction of the catalog, or price moves beyond a set percentage, stop and page the merchandiser with the exact operation list. The merchandiser approves, trims, or rejects. A person cannot review 4,000 products a night, and should not. Reviewing the one abnormal diff a month is the whole job, and it is the difference between a sync and an incident.
Agent Capabilities
10 actionsCatalogs
3- List Catalogs Lists the product catalogs owned by a Meta Business with ID, name, and product count. The resolution step that supplies the catalog ID every other operation needs.
- Get Catalog Retrieves one catalog's name, product count, and vertical. Falls back to the configured Default Catalog ID when none is supplied.
- Create Catalog Creates a new catalog under the business and returns its ID. Requires admin access to the Business Manager; used when a workflow provisions a catalog per brand or region.
Products
6- List Products Pages through a catalog's products with ID, retailer_id, name, price, and availability. The state-reading half of every diff and audit.
- Get Product Retrieves one product by its numeric Graph API ID, with name, price, availability, and images. Note the distinction: this takes the Graph ID, not your retailer_id.
- Create Product Adds a single product with your retailer_id as its stable SKU key, price in minor units with an ISO currency code. The right call for one-off launches; feeds belong in Batch Items.
- Update Product Changes only the fields you supply on a product identified by Graph API ID. Used for surgical corrections between sync runs.
- Delete Product Permanently deletes one product from its catalog. Cannot be undone, and on this page it fires only from an approved list.
- Batch Items Creates, updates, or deletes many products in one call: UPDATE to create or replace, DELETE to remove, each keyed by retailer_id. Inside data objects, availability and condition use raw API values and prices use minor units. The engine of feed sync, and the action the human gate watches hardest.
Product Sets
1- List Product Sets Lists a catalog's product sets with ID, name, product count, and filter. Product sets are the filtered subsets that power specific ads and Shop sections, so this is how audits map catalog problems to campaign impact.
Frequently Asked Questions
What can FlowRunner do with Facebook Catalogs?
FlowRunner agents can run List Catalogs, Get Catalog, and Create Catalog in Facebook Catalogs, plus 7 more actions.
Does connecting Facebook Catalogs to FlowRunner require OAuth?
No. Facebook Catalogs connects to FlowRunner with an API key, no OAuth flow required.
Can Facebook Catalogs trigger a FlowRunner workflow automatically?
Facebook Catalogs doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Facebook Catalogs
$100 in credits. No card required. Connect in minutes.