---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up bi-directional webhook for the GitHub spoke

# Set up bi-directional webhook for the GitHub spoke {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Configure webhook to subscribe to GitHub with a ServiceNow callback
URL.

## Before you begin

* Request Integration Hub subscription
* Activate the GitHub spoke
* Role required: admin
{#setup-biwebhoook-github__ul_xl3_c55_z3b}

## Register GitHub webhook in ServiceNow {#ariaid-title2}

Register a GitHub in ServiceNow to notify the ServiceNow app when certain events occur in GitHub.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllGitHub WebhooksGitHub Webhook Registries.
2. Click New.
3. On the form, fill in the fields.  
   {#reg-githubwh__table_w1l_s55_z3b__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique name to identify the record. For example, <kbd class="ph userinput">GitHub webhook</kbd>. |
   | Description | Description of the record. |
   [Table 1. GitHub Webhook Registry form]

   {#reg-githubwh__table_w1l_s55_z3b}
4. Right-click the form header and click Save.
5. Click Callback URL.  
   The system displays the Webhook Callback URL and Webhook Secret.

6. Copy and record the values of Webhook Callback URL and Webhook Secret.
{#reg-githubwh__steps_wv4_wgh_jkb}

### Result

The GitHub webhook is registered in your ServiceNow instance.

## Add Callback URL in GitHub {#ariaid-title3}

Provide Webhook Callback URL in GitHub account to create webhook.

### Before you begin

Role required: admin

### Procedure

1. Log in to your GitHub account.
2. Navigate to the required repository.
3. Select Settings.
4. On the left panel, select, Webhooks.
5. Select Add Webhook.
6. Enter Webhook Callback URL in Payload URL and Secret in Secret.  
   See the [GitHub Developer](https://developer.github.com/) documentation for instructions on creating and configuring a webhook.  
   Note:  
   GitHub spoke supports application/json payload. Configure the GitHub webhook accordingly. See the [GitHub Developer](https://developer.github.com/) documentation for instructions on creating and configuring a webhook.

### Result

The Callback URL is added in the GitHub account. You can create routing policies and subflows as per your requirement. See [Customize a bi-directional webhook](https://www.servicenow.com/docs/wwlR8uFMUD89A7FoEbdv0w#customize-routingpolicy "Create a webhook routing policy and subflow as per your requirement.") for information regarding creating new routing policies and subflows.

## Customize bi-directional webhook in the GitHub spoke {#ariaid-title4}

Create webhook routing policy and subflow as per your requirement in the GitHub spoke.

### Before you begin

Role required: admin

### About this task

The default routing policy in the GitHub WebHook Routing Policies modules triggers the relevant GitHub subflow and notifies the ServiceNow app when certain events occur in GitHub. See [GitHub Spoke](https://www.servicenow.com/docs/tlccIuHOE16DKLk5FiMY5g "Manage distributed version control and source code in GitHub from your ServiceNow instance. Create flows in ServiceNow to manage collaborative features such as tracking bugs, feature requests, tasks and so on, for projects in GitHub. View and analyze meaningful usage data for GitHub Enterprise Cloud and GitHub Enterprise Server software subscriptions so that you can reclaim stale licenses.") for information about the GitHub fields that the default routing policy supports and the GitHub events that the subflows support. To use any other fields in your custom subflow and customize conditions in the routing policy, perform these steps.

### Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. Click Subflows.
3. Create a copy of the required subflow.
4. Customize the required subflow as per your requirement and publish it.  
   See [Building subflows](https://www.servicenow.com/docs/access?context=subflows&version=brazil&pubname=brazil-build-workflows&ft:locale=en-US) for more information about creating and using subflows and [GitHub Spoke](https://www.servicenow.com/docs/tlccIuHOE16DKLk5FiMY5g "Manage distributed version control and source code in GitHub from your ServiceNow instance. Create flows in ServiceNow to manage collaborative features such as tracking bugs, feature requests, tasks and so on, for projects in GitHub. View and analyze meaningful usage data for GitHub Enterprise Cloud and GitHub Enterprise Server software subscriptions so that you can reclaim stale licenses.") for information about the GitHub fields that the default routing policy supports and the GitHub events that the subflows support.
5. Navigate to GitHub WebhooksGitHub WebHook Routing Policies.
6. Click New.
7. On the form, fill in the fields.  
   {#customize-webhook-github__table_awj_xgv_z3b__entry__2}

   | Field | Description |
   |-|-|
   | Label | Unique label to identify the routing policy. |
   | Default answer | Option to specify if this is the default answer. Default answer is applicable when the conditions are not met. |
   | Condition | Conditions to be met when the required events occur in GitHub. See [GitHub Spoke](https://www.servicenow.com/docs/tlccIuHOE16DKLk5FiMY5g "Manage distributed version control and source code in GitHub from your ServiceNow instance. Create flows in ServiceNow to manage collaborative features such as tracking bugs, feature requests, tasks and so on, for projects in GitHub. View and analyze meaningful usage data for GitHub Enterprise Cloud and GitHub Enterprise Server software subscriptions so that you can reclaim stale licenses.") for information about the supported fields. |
   | Answer | Subflow that has to be triggered when the specified conditions are met. 1. Click the Lookup icon. 2. Select the required subflow from the Document: list. Note: Ensure that the Table name is <kbd class="ph userinput">Flow [sys_hub_flow]</kbd>. {#customize-webhook-github__ol_sdf_ftb_1jb} |
   [Table 2. Decision form]

   {#customize-webhook-github__table_awj_xgv_z3b}
8. Click Submit.  
   Note:  
   These routing policies are saved in the Decision tables. Users are cautioned against directly updating or modifying data in these tables.
{#customize-webhook-github__steps_mxc_v3h_jkb}

### Result

Routing policy and subflow are created.

*[\>]: and then