This page is for admins who make Buttons.

In this guide, a Zap tells the user about its steps. After each step, the Zap sends a custom message to OneClick. The
user reads the messages in the OneClick Panel. For all the details of messaging, see
[Messaging](/docs/buttons/workflow-button/sections/messaging).

Start with a Zap that a Workflow button starts, for example the Zap from
[Start a Zap](/docs/using-oneclick-with/zapier/start-a-zap). The Zap gets the request with a **Catch Hook**
trigger.

## Turn on messaging for the Button

Zapier cannot send its own HTTP answer to OneClick. The Zap sends custom messages instead.

1. Open the Button in the Button editor.
2. Turn on the switch at the right of **Messaging** in the menu.
3. Click **Messaging**.
4. Turn on **Do not log HTTP responses**. The answer of the webhook then does not make a message.
5. Click **Save**.
6. Close the Settings.
7. Click the Button in the OneClick Panel of a deal. The request now contains `event_id`.

## Get the event ID 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 `event_id`.

OneClick uses the event ID to show the message to the correct user, on the correct Button and record.

## Add a custom message

Add a message after each step of the Zap that the user must know about.

1. Add an action after the step.
2. Select **Webhooks by Zapier** as the action app.
3. Select **POST** as the action event.
4. Type the URL of the messaging end-point in the URL of the action. The
   [Messaging](/docs/buttons/workflow-button/sections/messaging#custom-messages) page gives the URL.
5. Set the payload type to `json`.
6. Add the key `message` with the text of the message.
7. Add the key `message_type` with the type of the message, for example `success`.
8. Add the key `event_id`. Select `event_id` from the data of the trigger as its value.
9. Publish the Zap.

![The data of a Webhooks by Zapier POST action with the keys message, message_type and event_id](https://res.cloudinary.com/zimple/image/upload/f_auto,q_auto/oneclick-docs/using-oneclick-with/zapier/send-messages-from-a-zap/third-party-webhook-data.png)

The type of a message is `info`, `success`, `warning` or `error`. For the keys and the rules of a custom message, see
[Custom messages](/docs/buttons/workflow-button/sections/messaging#custom-messages).

## Test the Button

1. Open a deal in Pipedrive.
2. Click the Button in the OneClick Panel.
3. Make sure that the Panel shows the messages of the Zap. See [Read messages](/docs/use-buttons/messages).

## Stop a second press after an error

A Zap that stopped with an error usually stops again at the next press. You can block the Button until the user reads
the error message.

1. Send the message of an error step with the `message_type` `error`.
2. Open the Button in the Button editor.
3. Click **Messaging** in the menu.
4. Turn on **Disable the button if there are unread error messages**.
5. Click **Save**.

The user can press the Button again after the user reads the error message. See
[Disable the button if there are unread error messages](/docs/buttons/workflow-button/sections/messaging#disable-the-button-if-there-are-unread-error-messages).

To send a different message for a success and for an error, use Zapier paths.