This page is for admins who make Buttons.

In this guide, you add fields to a Workflow button. The Zap then uses the values of the fields in the content of a
deal note.

Start with the Zap and the Button from [Start a Zap](/docs/using-oneclick-with/zapier/start-a-zap). The Zap
gets the request with a **Catch Hook** trigger and adds a note with a Pipedrive **Create Note** action.

## Add fields to the Button

1. Open the Button in the Button editor.
2. Add the fields that the note needs. See [Add a field](/docs/buttons/workflow-button/sections/custom-fields#add-a-field).
3. Click **Save**.
4. Close the Settings.
5. Click the Button in the OneClick Panel of a deal. OneClick sends a request with the field values to the Zap.

## Get the field values in the Zap

1. Go back to the Zap.
2. Open the test of the **Catch Hook** trigger.
3. Load the new requests of the webhook.
4. Select the request of your last press. The data now contains `fields`.

The values are in `fields`, in one object for each type of field: `deal`, `organization`, `person` and `disposable`.
Each field has its key, for example `fields` > `deal` > `title` > `field_value`. See
[The data that the Button sends](/docs/buttons/workflow-button/sections/custom-fields#the-data-that-the-button-sends).

The key of a Pipedrive standard field is its name in the Pipedrive API, for example `title`. The key of a Pipedrive
custom field is a long code. The key of a disposable field is the **Field key** of the field.

## Add the values to the note

1. Open the **Create Note** action.
2. Edit the content of the note.
3. Select the field values from the data of the trigger, for example the `field_value` of a field.
4. Publish the Zap.

## Test the Button

1. Open the deal in Pipedrive.
2. Click the Button in the OneClick Panel.
3. Fill in the fields, if the Button shows fields that the user fills in.
4. Make sure that the deal shows a note with the field values.