Product List
Product List presents a browsable catalog through WhatsApp's native product interface. The customer browses items — each with its own thumbnail, description, and price — adds selections to a cart, and submits. The selection data is captured as a conversation variable for downstream processing.
This node requires WhatsApp. It relies on Meta's Commerce Catalog feature and has no web implementation.
When to Use It
Product List fits any scenario where customers need to choose from a catalog of items with rich visual presentation. The WhatsApp product interface shows images, descriptions, and prices in a familiar shopping format.
Some examples: equipment financing where customers browse trucks or machinery before applying for credit. Auto parts where a retailer selects items from a distributor's catalog. FMCG where a small business browses wholesale inventory and places a financed order.
Configuration
| Option | Description |
|---|---|
filterByCategory | Category to filter which products appear in the catalog |
The dropdown loads categories from the Commerce Products API. Results are capped at 30 products.
Output Handles
| Handle | When |
|---|---|
| Success | Customer submitted a selection |
| Error | Missing catalog configuration, no products in category, or API failure |
The Selection Variable
When the customer submits, a variable is created containing their selections — SKUs, quantities, prices. The variable name is dynamic, incorporating the catalog ID and timestamp (e.g., order-CATALOG123-1705123456). This means you cannot reference it with a static name like {{order}}. Plan accordingly when designing downstream nodes that need to process the selection.
Prerequisites
The node requires a Meta Commerce Catalog configured and linked to the WhatsApp Business Account. Connector secrets must include the catalog_id and access_token. Products must exist in both Meta's catalog and the internal database with matching SKUs — if they're out of sync, results will be unpredictable.
Things to Know
No built-in validation. The node accepts whatever the customer submits. Validate quantities, availability, or credit limits in subsequent nodes using Conditional or Workflow Execute.
Exact category matching. Products must belong to the exact category specified — there's no fuzzy matching or fallback.