Git Integration for Jira Cloud Documentation

Webhook indexing integration

The Git Integration for Jira Cloud app offers an integration type called Webhook Indexing.

The classic full feature Git service integration gives you access to all features for the connected git servers. However, it requires two-way communication originating from outside your network. Therefore, you need to allow incoming requests by updating your network/firewall settings. For more information, see Allow list (whitelist) GIJ Cloud.

Webhook indexing integration allows your connected git servers to work behind a firewall. This is its main advantage. However, the integration has limited features as stated in the Connect to your Git server features table.

On this page:

What is Webhook Indexing?
How does Webhook Indexing work?
How do I configure Webhook Indexing?
Supported webhook indexing integrations
Frequently Asked Questions

What is Webhook Indexing?

In the Classic Indexing options, all features are available (explained here: Classic Indexing Explainer) but require two-way communication originating from outside your network (see Allow list (whitelist) GIJ Cloud). Webhook Indexing only requires that your Git server can make outbound Internet requests.

How does Webhook Indexing work?

With Webhook Indexing, the system uses the git metadata available in the git server webhook payload to index the commit, branch, and pull request (git tag support coming soon). A Jira administrator creates a “Webhook indexing” integration, selects the Git server type (GitHub, GitLab, Azure DevOps, etc), and then configures the Git server to send webhooks to a unique and password-protected address hosted by the Git Integration for Jira Cloud app.

How do I configure Webhook Indexing?

Configuring Webhook Indexing begins with the Jira administrator installing the Git Integration for Jira Cloud app. Click the “Webhooks” limited feature connection option and select your git server type. In your git server, create a new webhook by copying the webhook URL and secret from the Webhook Indexing wizard. That’s it! Now all future commit, branch, and pull/merge request activity will be indexed by the Git Integration for Jira Cloud app.

Tip!
Set up the webhook at the organization/group/project level in your git server to configure webhooks for multiple git repositories at once.

Supported webhook indexing integrations

GitHub webhook indexing integration SUPPORTED
GitLab webhook indexing integration SUPPORTED
Microsoft webhook indexing integration SUPPORTED
Gerrit webhook indexing integration SUPPORTED

Frequently Asked Questions

What git servers does the Webhook Indexing feature support?

What data does a webhook send?

Each git server is different, but generally webhooks from leading git server vendors such as GitHub, GitLab, and Azure DevOps include the following:

Repository URL
Repository name
Commit URL
Commit author name
Commit author email
Commit SHA
Commit message
Files changed
Other metadata

Webhook payloads from leading git server vendors do not include source code.

How is Webhook indexing different from Indexing triggers?

Previously, the application called Indexing triggers “Webhooks.” Indexing triggers simply trigger a reindex of a repository in a “Classic” integration to update Jira Cloud with commits, branches, pull requests, and tags (see Indexing Triggers).

If webhooks are sent only once by my git server, what happens if Git Integration for Jira Cloud is down?

The Webhook indexing feature automatically scales to any number of webhooks sent for indexing using enterprise-grade AWS services. A separate highly-available AWS service queues these webhooks until the system indexes them and sends them to Jira Cloud. This architecture means the system receives webhooks even if the Git Integration for Jira Cloud application is down for maintenance (see BigBrassBand Cloud Status) or if indexing webhooks slows down. If the Git Integration for Jira app is unavailable for a period of time, the system processes the webhooks when the Git Integration for Jira Cloud app comes back online.

What happens if my git server is down for a period of time and suddenly sends thousands of webhooks in a short burst?

If webhooks are sent only once by my git server, what happens if the webhook format changes and the Git Integration for Jira Cloud app does not recognize the format?

The system stores webhook payloads in case they need reprocessing. Future enhancements to the Webhook Indexing features may allow Jira administrators to reprocess webhook payloads.

What if I want to delete all of my data in the Git Integration for Jira Cloud app?

Jira administrators can remove all git integration data by removing the integration. This deletes the data from BigBrassBand production servers immediately. BigBrassBand maintains backups including customer data for 7 days, after which the system deletes the backup data.

When I tested Webhook Indexing, I noticed that webhooks receive a 202 response. Why?

The HyperText Transfer Protocol (HTTP) 202 Accepted response status code communicates that the server accepted the request for processing, but processing has not completed; in fact, processing may not have started yet. We provide this response because a highly-available AWS service (separate from the Git Integration for Jira Cloud indexing process) receives the webhooks. In practice, Jira users can view Webhook indexing updates in Jira Cloud within a few seconds.

What security precautions does BigBrassBand take to secure my data?

See: Security & Trust

What are the limitations of Webhook indexing?

Webhook indexing relies on git server webhooks, which are only sent for new activity. This means the git server cannot resend previous pushes containing commit, branch, and pull request activity. Historical repository information is not available through Webhook indexing.
Git servers have different webhook sending behaviors. GitHub limits a webhook to 1000 commits in a single push. Azure DevOps limits a webhook to 25 commits in a single push. GitLab limits a webhook to 20 commits in a single push. We recommend communicating these limitations to developers on your teams.
Because webhooks do not include source code, the code review capabilities available in Classic Indexing integrations are not available.
For more details, see Feature matrix of Git Integration for Jira Cloud.

I have more questions about Webhook indexing

Please reach out to us at [email protected] or via our Support Portal.

Last updated: December 2025

Have feedback about this article? Did we miss something? Let us know!