# From Dockerhub events

thatSuppose users want to trigger a pipeline or release on the successful push of an image on a registry on **Dockerhub,** they can create a webhook using the webhook type as Dockerhub.

### **Steps to create a Dockerhub Webhook for release** <a href="#steps-to-create-a-dockerhub-webhook-for-release" id="steps-to-create-a-dockerhub-webhook-for-release"></a>

**Pre-requisites:**

* An active Dockerhub account with registries needs to have the PAT which can be entered while creating Dockerhub integrations
* An Active cluster
* A Release that has been created from the Release Templates section

**Steps**

1. On click of the **create webhook** button, a modal window appears in which we can enter the details for webhook creation

<figure><img src="/files/DwRG3xknqbIsGGUQOdeZ" alt=""><figcaption></figcaption></figure>

2. Now we need to select the Webhook Type as Dockerhub from the **Webhook Type** dropdown

<figure><img src="/files/NIcbDuwi7pM34p8bgjw7" alt=""><figcaption></figcaption></figure>

3. After selecting the webhook type as **Dockerhub**, a dropdown will be shown to select the registry for which the webhook needs to be created

<figure><img src="/files/QDXZRfXz2yjpVoTi8o0X" alt=""><figcaption></figcaption></figure>

4. After selecting the Registry, select the **option type** as push

<figure><img src="/files/RQvFTVZYxpsNz8lVhUuR" alt=""><figcaption></figcaption></figure>

5. Once the action type has been selected, select the trigger type as **release.**

<figure><img src="/files/RhKeDZq8jenwDQ45Ghgs" alt=""><figcaption></figcaption></figure>

6. After this users can select the release which they want to be triggered

<figure><img src="/files/kky09OnjD4WdSA3eIuse" alt=""><figcaption></figcaption></figure>

7. Once every option have been selected the **map parameters** option will be enabled and users can click on it to move to the next step

<figure><img src="/files/5O6b0g0Cr3uwXJtLa7Tz" alt=""><figcaption></figcaption></figure>

8. After going to the second step users can choose the **input run parameters**, once all these options have been selected, users can click on the save button to create the webhook

<figure><img src="/files/eki3w6qd4LhgO0dQ8VME" alt=""><figcaption></figcaption></figure>

9. Once the user clicks on save, the webhook has been created and is seen in the table list view

<figure><img src="/files/kSzMyKA6CHZLb6wBYL7K" alt=""><figcaption></figcaption></figure>

Users can click on the edit button to edit the webhooks, click on the toggle button to enable/disable the webhook, and as it is seen from the webhook type that it is a Dockerhub webhook.\
\
**Steps to create Dockerhub webhook for pipeline**

**Pre-requisites:**

* An Active cluster
* A microservice

Follow the same steps until **Step 4** of Creating Webhooks for release

**Steps:**

1. Once the registry and the action type have been selected, select the release type as the pipeline

<figure><img src="/files/CuuCQZu6LKXuYVbLXYwe" alt=""><figcaption></figcaption></figure>

2. Once the Trigger type has been selected, now select the pipeline that needs to be triggered

<figure><img src="/files/xla5a4joPfxR9KbPt8ra" alt=""><figcaption></figcaption></figure>

3. After selecting the pipeline, select the environment in which the webhook needs to be created\
   **Remember to select the environment the same in which the cluster has been created**

<figure><img src="/files/lkThLHzXgiXyIbAThamW" alt=""><figcaption></figcaption></figure>

4. After selecting the environment, users will be shown an option to select the cluster

<figure><img src="/files/GaqUwroY01owiay5kZoh" alt=""><figcaption></figcaption></figure>

5. Once the cluster has been selected, select the microservice

<figure><img src="/files/cbnKqQUG23j616bxyNDv" alt=""><figcaption></figcaption></figure>

6. After selecting the microservice, users can move to the **Map parameters** step, to select the run parameters for the pipeline

<figure><img src="/files/gu5K9vwhNAX6h33UFLnf" alt=""><figcaption></figcaption></figure>

7. In **Map parameters,** users can select all the options as they desire

<figure><img src="/files/nQmjqUK8ezvWIflpUFnQ" alt=""><figcaption></figcaption></figure>

8. Once all this is done, users can click on the **Save** button to create the webhook for the pipeline.

<figure><img src="/files/DoB4xwqgG5vZRAF6I88z" alt=""><figcaption></figcaption></figure>

9. Once the webhook has been created successfully, it is shown in the webhooks list view

<figure><img src="/files/EXHDXzG8T9jPhRKKsQyk" alt=""><figcaption></figcaption></figure>

Users can edit the webhook from the edit option, and click on the toggle window to enable/disable the webhooks, as well as it can be seen from the webhook type that it is a Dockerhub webhook.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/triggers/triggering-a-pipeline-and-or-a-release-run/from-dockerhub-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
