# How to Show WhatsApp Catalog Products in ZazzyAgent Flow Builder

Once your WhatsApp catalog is connected to [ZazzyAgent](http://app.zazzyagent.com), you can use it inside a Flow Builder automation.

This allows customers to browse products as part of a conversation.

A simple flow can look like:

```text
Customer
   ↓
Trigger
   ↓
Interactive Message
   ↓
Catalog
   ↓
Product Selection
   ↓
Next Step
```

## Before you begin

Make sure:

*   WhatsApp is connected.
    
*   Your catalog exists.
    
*   Products have been added.
    
*   The catalog is available to the connected WhatsApp account.
    

See [How to Connect a WhatsApp Catalog to ZazzyAgent](https://blog.zazzyagent.com/how-to-connect-whatsapp-catalog-zazzyagent).

## Step 1: Create a Flow

Open Flow Builder.

Create a new flow.

Give it a useful name.

For example:

> Product Catalogue

rather than:

> Test 7

## Step 2: Add a trigger

Choose the appropriate trigger for your flow.

For example:

> products

This lets a test customer start the flow by sending:

> products

## Step 3: Add an Interactive Message

Add the appropriate Interactive Template/message component.

This provides the introductory part of the catalog experience.

Example:

> Here are some of our available products.

## Step 4: Connect the Catalog

Use the ecommerce/catalog connection from the interactive component.

Add the Catalog component.

The current configuration workflow connects the interactive component's ecommerce section to the Catalog element.

## Step 5: Select your catalog

Open the Catalog component.

Choose the catalog you've connected to your WhatsApp setup.

## Step 6: Choose how many products to show

You can configure the catalogue to present individual products or multiple products.

### Single product

Use when you know exactly which product should be displayed.

### Multiple products

Use when customers need to browse several products.

The current catalogue component supports both approaches.

## Example: One product

Customer:

> Tell me about Product A.

Your flow:

```text
Customer
   ↓
Product A
   ↓
Catalog
   ↓
Product A
```

The customer sees the relevant product from the connected catalog.

## Example: Multiple products

Customer:

> Show me your products.

Your flow displays several products.

The customer can browse them and select the one they're interested in.

## Step 7: Create the next step

Think about what should happen after the customer interacts with the catalog.

For example:

**Product selected**

→ Send additional information

or:

**Product selected**

→ Start another flow

or:

**Product selected**

→ Continue to an AI assistant

The right choice depends on your use case.

## Example: Product information

```text
Catalog
   ↓
Customer selects product
   ↓
Product information
   ↓
Ask if they need help
```

## Example: Lead generation

A customer sees a service/product.

Then:

> Would you like a quotation?

**Yes**

→ Lead form.

**No**

→ Continue browsing.

## Example: AI-assisted product enquiry

```text
Customer
   ↓
AI Agent
   ↓
Understands interest
   ↓
Relevant catalog
   ↓
Customer selects product
   ↓
Continue conversation
```

This can make the catalog feel like part of a conversational shopping assistant.

## Don't duplicate the catalog into your flow

The purpose of using the Catalog component is to reference the structured catalog.

Don't manually recreate all product information in text nodes unless there's a specific reason.

## Update products in the catalog

If:

> Product A price changes.

update Product A in your connected catalog.

Your Flow doesn't need to become a second product database.

## Multiple product sections

For broader catalog presentations, organize products logically.

For example:

**Shoes**

**Shirts**

**Accessories**

Instead of showing unrelated products all at once.

The current catalogue workflow supports product sections and multiple-product configurations.

## Use the catalog after a category selection

A useful pattern is:

```text
What are you looking for?
       ↓
[Shoes]
[Clothing]
[Accessories]
       ↓
Relevant Catalog
```

This creates a much cleaner customer experience than displaying your entire catalog immediately.

## Catalog and customer intent

A catalog should appear at the right point in the conversation.

Don't send a product catalog to someone who is asking:

> How do I contact support?

Use conditions, routing or AI to determine whether the customer is actually looking for products.

## Test the flow

Test:

*   Trigger
    
*   Interactive message
    
*   Catalog
    
*   First product
    
*   Other products
    
*   Next step
    

Make sure each path behaves correctly.

## Common problems

### Catalog component is empty

Check the connected catalog and Meta access.

### Product isn't available

Check whether the product belongs to the selected catalog.

### Wrong product appears

Check your product selection in the Catalog configuration.

### Updated product information isn't showing

Check the catalog itself and allow the updated information to propagate.

## A clean architecture

```text
Customer Intent
      ↓
Flow
      ↓
Interactive Message
      ↓
Catalog
      ↓
Relevant Product(s)
      ↓
Customer Selection
      ↓
Next Automation
```

The Catalog should be treated as a structured data source inside your conversational workflow—not as a replacement for the Flow Builder itself.