Catalog

The Catalog node renders a tenant product catalog as cards or a list, and captures the customer’s pick into a recipe variable.

Configuring the node

1. Drop the Catalog node from the Commerce category onto the canvas.
2. Open the configuration drawer:
   • Catalog ID — the UUID of the catalog to render. Catalogs are managed by admins under Settings → Catalogs.
   • Selection variable key — recipe variable that captures the picked item’s SKU when the customer selects a card.
   • Max items — how many items render in a single send. Capped at 30 server-side; 10 is a reasonable default.
   • Layout — list or carousel.

Output port

• next — the recipe continues after the catalog is sent. The customer’s selection is written to the configured variable for downstream branching.

Where it’s used

Use Catalog when you have a stable, managed list of items (plan options, FAQs grouped as items, network hospitals) and want a single canonical surface for picking among them. Editing a catalog at Settings → Catalogs immediately changes what the node renders — no recipe change required.

Best practices

• Keep catalogs short enough that the customer doesn’t have to scroll endlessly. Use Condition nodes upstream to narrow the catalog by region, plan, or category before rendering.
• Use the carousel layout for ≤ 5 items where each option deserves an image. Use the list layout for longer answer sets where titles are the primary differentiator.
• Branch on the selection variable downstream — pair the Catalog node with a Condition node that routes based on the picked SKU.