This page is for admins who make Buttons.

The **Products** section adds the products of a deal to the request of a Workflow button. Your process then does
not have to get the deal products from Pipedrive. The section can also require that the deal has a product.

A Floating window Button has no **Products** section.

## Include the deal products

1. Open the Button in the Button editor.
2. Click **Products** in the menu.
3. Turn on **Include deal products**.
4. To stop a press on a deal without products, turn on **Require at least 1 product**.
5. Click **Save**.

The menu then shows **On** at the right of **Products**. When the products are required, it shows **Required**.
**Require at least 1 product** is available only when **Include deal products** is on.

![The Products section of the Button Create invoice with Include deal products and Require at least 1 product on, and Required in the menu](https://res.cloudinary.com/zimple/image/upload/f_auto,q_auto/oneclick-docs/buttons/workflow-button/sections/products/products-section.png)

## The data that the Button sends

A press on a deal adds the key `products` to the body of the request. The value is the list of the products of the
deal. The list has the format that the Pipedrive API gives for the API version of the Button. See
[Migrate to API v2](/docs/buttons/migrate-to-api-v2).

## Products on a person or an organization

A person and an organization have no deal products. A press there sends no `products` key, and OneClick does not
require a product. To show the Button only on deals, use [Limit visibility](/docs/buttons/limit-visibility).

## A deal without products

When **Require at least 1 product** is on and the deal has no product, OneClick does not send the data. The user
sees **Deal products are required. Please add at least 1 product and try again.** For the view of the user, see
[Press a Button](/docs/use-buttons/press-a-button#steps-before-oneclick-sends-the-data).