Skip to main content
The Products module lets you register the catalog of items sold by your operation and make it available to AI agents and to the sales pipeline. Each product can have variants (size, color, plan, etc.) and can be linked to pipeline items to track ongoing sales opportunities.
Available starting in v1.0.0-rc3.

What is the Products Catalog?

The catalog is a central list of products in your operation. Instead of keeping that information scattered (spreadsheets, external integrations, prompts pasted manually), you keep a single source inside the CRM. When the AI agent needs to talk about an offer, it consults this catalog. When a conversation becomes an opportunity, you link the product to the corresponding pipeline item.

How Products Work

Each product has:
  • Basic info: name, description, price, status (active/inactive).
  • Variants: different versions of the same product (e.g., “Basic Plan”, “Pro Plan”, “Enterprise Plan”), each with its own price and SKU.
  • Agent binding: you choose which agents have access to which products. Linked products are injected into the agent’s context at conversation time.
  • Pipeline binding: inside a pipeline item (an opportunity), you record which product is being negotiated. Useful for per-pipeline sales reporting.

Common Use Cases

  • Sales via WhatsApp: the agent knows the catalog and answers prices/variants without operators having to paste tables into the prompt.
  • Funnel tracking: each pipeline conversation records the product under negotiation, allowing conversion measurement per product.
  • Per-agent product portfolio: different teams (sales, support, retention) can have agents with distinct catalogs.

Accessing the Products Module

Access is via the platform’s main menu, under Products.
Menu visibility depends on the products.read permission in your role. If the entry doesn’t appear, ask the administrator to grant it (see Custom Roles).

Creating a Product

On the catalog screen, click New Product to open the form. Required fields:
  • Name — how it appears to the agent and to the operator.
  • Description — short explanation used by the agent to contextualize the offer.
  • Status — active (available for sale) or inactive (does not appear in selectors).
Optional fields:
  • Base price — reference used when there is no variant.
  • SKU — inventory code, if applicable.

Working with Variants

Variants represent versions of the same product with distinct attributes (price, characteristics, SKU). Examples:
  • Software plan: “Basic”, “Pro”, “Enterprise” — different prices, same root product.
  • Apparel: “S”, “M”, “L” — different SKU and stock.
  • Course: “Monthly”, “Yearly” — different periodicity and price.
Each variant has its own name, price, and optional SKU. When an agent talks about a product that has variants, it presents the options and helps the customer choose.

Linking Products to Agents

In the agent configuration screen, there is a Products tab. There you choose which catalog items the agent knows about. Only products with active status are available for linking. When you link, the catalog is injected into the agent’s context at runtime. This means changes in the catalog (price, description, new variant) reflect in the next agent conversation, without reconfiguring the prompt. See details in Agent Configuration.

Linking Products to Pipeline Items

Inside the pipeline item detail, there is a Sale panel where you record:
  • Which product is being negotiated.
  • Which variant (if any).
  • Negotiation value (may differ from the catalog price in case of discount).
The AI agent can also do this binding automatically during a conversation, using the native tool link_product_to_pipeline_item. When the customer confirms interest in a specific item, the agent records the link without manual intervention.

Permissions

Access to the module is controlled by three permissions on the products resource: By default, account_owner gets manage and agent gets read. Custom roles can have any combination. See Custom Roles.

Final Considerations

The products catalog:
  • Centralizes offer information in a single place.
  • Connects AI agents to what your company actually sells.
  • Couples the sales pipeline to the catalog, enabling conversion reports.
For the step-by-step on linking the catalog to the agent, see Agent Configuration. For recording sales in the pipeline, see Managing Pipelines.