--- title: Set up triggers for the Jenkins spoke description: Set up triggers for the Jenkins spoke for the required events. The endpoint enables webhooks to connect with your ServiceNow instance.Configure endpoint for webhooks in the Jenkins that support the token authentication.Create a pipeline projects in Jenkins to add the endpoint URL in Jenkinsfile that is generated in your ServiceNow instance and enable webhooks to connect with your ServiceNow instance. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/integration-hub/jenkinsv2-triggers.html release: australia product: Integration Hub classification: integration-hub topic_type: task last_updated: "2026-03-28" reading_time_minutes: 2 breadcrumb: [Jenkins v2 Spoke, Integration Hub spokes, Build integrations, Integration Hub, Workflow Data Fabric] --- # Set up triggers for the Jenkins spoke Set up triggers for the Jenkins spoke for the required events. The endpoint enables webhooks to connect with your ServiceNow instance. ## Before you begin Role required: admin ## Configure triggers in ServiceNow instance Configure endpoint for webhooks in the Jenkins that support the token authentication. ### Before you begin Role required: flow\_designer and connection\_admin ### Procedure 1. Navigate to **All** > **Process Automation** > **Workflow Studio**. 2. Click the **Integrations** tab. 3. Toggle and enable the **Inbound** connections. 4. Locate the **JenkinsV2 Spoke** endpoint and click **View Details**. \[Omitted image "jenkinsv2-ext-triggers1.jpg"\] Alt text: 5. For the **JenkinsV2 External Trigger** end point, click **Configure**. \[Omitted image "jenkinsv2-ext-triggers2.jpg"\] Alt text: 6. Select the user who can trigger the endpoint and click **Activate**. \[Omitted image "jenkinsv2-ext-trig3.jpg"\] Alt text: 7. Copy the generated endpoint URL. \[Omitted image "jenkinsv2-ext-trig4.jpg"\] Alt text: ## Create a pipeline project in Jenkins Create a pipeline projects in Jenkins to add the endpoint URL in `Jenkinsfile` that is generated in your ServiceNow instance and enable webhooks to connect with your ServiceNow instance. ### Before you begin - Ensure that you install Jenkin in the local environment. - Ensure that Maven and GitHub are installed in the Jenkins account. - Ensure that these plugins are installed in the Jenkins account. - Pipeline - Git plugin - Git client - Http request - Credentials - Warnings - Coverage - In GitHub, generate a classic personal access token and copy the value. Ensure that you select the scopes for the personal access token. - repo - repo:status - repo\_deployment - public\_repo - repo:invite - security\_events - write:packages - read:packages For more information about creating a classic personal access token, see [Creating a personal access token \(classic\)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic) in [GitHub Docs](https://docs.github.com/en). For the list of supported events, see the [Spoke triggers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/jenkins-spoke.md) section. - Role required: admin ### Procedure 1. From the Jenkins Dashboard, select **+ New Item**. 2. On the form, enter a name to identify the pipeline and select **Pipeline**. 3. Click **OK**. The pipeline is created and its configuration options are displayed. 4. Under **Configure**, click **Pipeline**. 5. On the form, fill these values.
| Field | Description |
|---|---|
| Definition | Select **Pipeline script from SCM**. |
| SCM | Select **Git**. |
| Repository URL | Provide GitHub repository URL. |
| Credentials | Create the GitHub credential record and select it.1. Click **+Add**. 2. Select **Username with password** and click **Next**. 3. For **Username**, enter the GitHub username. 4. For **Password**, paste the personal access token that is generated in GitHub. 5. For **ID**, provide a unique ID to identify the credentials. 6. For **Description**, enter a description for the credentials. 7. Click **Create**. 8. Select this record for **Credentials**. |
| Branch Specifier \(blank for 'any'\) | Specify the required branch. |
| Script path | Relative location within the checkout of your Pipeline script.**Important:** In `Jenkinsfile`, paste the endpoint URL that was generated after you configured triggers in your ServiceNow instance. For more information, see [Configure triggers in ServiceNow instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/jenkinsv2-triggers.md). \[Omitted image "jenkinsv2-file.jpg"\] Alt text: |