# Triggering a pipeline and/or a release run When you want to trigger a release or a pipeline after a PR has been successfully merged or when code is pushed to a branch. Depending upon the use case you can create a webhook for their particular repository along with the pipeline or release that they want to trigger on the success of the event which can be the merging of a branch or pushing of code to a branch. Ozone provides the option to create **10 types** of **webhooks:** * Generic * Github * Gitlab * Azure Cloud Registry * Jira * Bitbucket * Slack * Harbor * Dockerhub * Azure DevOps **Pre-requisites:** You should have credentials for the providers for which you want to create the webhooks. ### **Steps to create a webhook** 1. On successful login, in the sidebar, you can see the option **Triggers**\
Open image-20240416-102827.png![image-20240416-102827.png](blob:https://ozonecloud.atlassian.net/b3afc018-d8e3-4864-9ed1-959e468bbae1#media-blob-url=true\&id=8a4a8d4e-cb01-4ad1-8b76-c964857299d9\&collection=contentId-2091745423\&contextId=2091745423\&mimeType=image%2Fpng\&name=image-20240416-102827.png\&size=211793\&width=1800\&height=1017\&alt=image-20240416-102827.png) 2. Once users click on **Triggers,** a modal window will be shown where you can click on **Webhooks**\
Open image-20240416-102941.png![image-20240416-102941.png](blob:https://ozonecloud.atlassian.net/dfba0f11-7ff7-4c16-86e5-782e17a4906d#media-blob-url=true\&id=dec2082b-d0c6-4e88-bf84-16d3790f44c9\&collection=contentId-2091745423\&contextId=2091745423\&mimeType=image%2Fpng\&name=image-20240416-102941.png\&size=212758\&width=1800\&height=1017\&alt=image-20240416-102941.png) 3. Once you click on **Webhooks**, they are taken to the Webhooks landing page, here a list of all the webhooks that have been created will be shown. Users can click on the **top right** to create a new webhook\
Open image-20240416-103325.png![image-20240416-103325.png](blob:https://ozonecloud.atlassian.net/df5a85b0-9e01-4e8b-bf2f-89187ad5515f#media-blob-url=true\&id=dec141be-f14c-4d1c-8062-8050ff3f8cb9\&collection=contentId-2091745423\&contextId=2091745423\&mimeType=image%2Fpng\&name=image-20240416-103325.png\&size=179603\&width=1800\&height=1017\&alt=image-20240416-103325.png) 4. Once the user clicks on the create webhook button a modal window appears where users can enter details to create a webhook\
Open image-20240416-113535.png![image-20240416-113535.png](blob:https://ozonecloud.atlassian.net/24f03530-6dfb-4664-8bf4-3e88d2a2f5f0#media-blob-url=true\&id=aa4db3b4-3010-4d3f-b0bb-46b87b8fae8d\&collection=contentId-2091745423\&contextId=2091745423\&mimeType=image%2Fpng\&name=image-20240416-113535.png\&size=230453\&width=1800\&height=1017\&alt=image-20240416-113535.png) Now to create a webhook for a particular type refer to the docs below - * Create a GitHub webhook
--- # 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.md?ask= ``` 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.