> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/triggers/triggering-a-pipeline-and-or-a-release-run/from-bitbucket-events.md).

# From Bitbucket events

thatSuppose users want to trigger a pipeline or release on successful Pull request merge on Bitbucket or when a code is pushed to a particular branch, they can create a webhook using the webhook type as **Bitbucket**.\ <br>

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

**Pre-requisites:**

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

&#x20;

**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/oAUETjJMlw8F6dNr38r9" alt=""><figcaption></figcaption></figure>

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

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

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

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

4. Once the repository has been selected, users have the option to select the event for which they want the pipeline or release to be triggered\
   Ozone offers **2 events** for which webhooks can be created:
   * Push branch - whenever code is pushed to the **specified branch** the webhook is triggered
   * Pull request - whenever a pull request is merged at that point the webhook will be triggered

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

5. After selecting the event, users are provided an option to **select the branch** for the repository for which they want the webhook to be triggered

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

6. since the branch has been selected, the next option which is provided for the users to select is whether they want to trigger a **release** or a **pipeline** on the successful happening of the event that they had selected

<figure><img src="/files/6NX26B6dAIwH6wG7dkU1" alt=""><figcaption></figcaption></figure>

Here we will select the option of **Release**

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

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

8. 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/Z7FiUfZwbZ0UtoDx9XZg" alt=""><figcaption></figcaption></figure>

9. 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/V7VuLScC9HWOK4WHJ0tM" alt=""><figcaption></figcaption></figure>

10. Once the webhook has been created, it will be shown in the tabular list view

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

The newly created webhooks are shown at the top of the list, as we can see the webhook type as **Bitbucket**, and the last triggered time is also shown. Users can also enable/disable the webhook from the toggle window, as well as click on the edit icon to edit the webhook.

### **Steps to create webhook for pipeline** <a href="#steps-to-create-webhook-for-pipeline" id="steps-to-create-webhook-for-pipeline"></a>

**Pre-requisites:**

* An Active cluster
* A microservice

Follow the same steps until **Step 5** of Creating Webhooks for release\
\
**Steps:**

1. Once the repository name and the branches have been selected select the trigger type as **Pipeline**

<figure><img src="/files/nmxSX3k3TTLV0UEtf1bR" 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/wdWolkMj23fL22av0nvS" 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/Q67Jgk1QpbkChFJMdFqJ" alt=""><figcaption></figcaption></figure>

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

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

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

<figure><img src="/files/2vCqGQVDdBilYtS9Zl5c" 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/0ZWdBXFCqhIcHW1JHFok" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/GwE015WqU428UcjrCfDN" 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/dxqleoEGuIS2VWyXe0y9" alt=""><figcaption></figcaption></figure>

9. The created webhook will be shown in the webhook list view

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

The last triggered time is also mentioned, along with this the webhook type is mentioned as **Bitbucket**.\
Users can click on the edit button to edit the webhook, click on the toggle button to enable/disable the webhook.