---
title: "Webhooks"
canonical: "https://support.appfire.com/space/FD/1802141845/Webhooks"
format: markdown
---
> ⚠️ Webhooks are only available in Flow Enterprise Server. Flow Cloud uses other mechanisms to increase ingestion speed for your integrations.

Webhooks are an additional integration service available for most Git integrations and may result in your commit, PR, and ticket data updating more frequently.

> ℹ️ Updates for organizations with large repos will take longer.

| **On this page:**<br>> Macro (toc) |
| --- |

## Permissions

Each Git host is different and there may be additional permissions needed to enable webhooks to work in Flow. Learn more about the necessary permissions for each [integration](https://appfire.atlassian.net/wiki/spaces/FD/pages/1802633269).

When you are attempting to enable webhooks within your Flow account, note that:

- For GitHub, Flow maintains webhooks at the organization level, not for individual repos.
- The service account used to establish the connection between Flow and the vendor must be the admin of the Git vendor organization or group.
- At least one repo from the vendor org must be imported.

## Enabling webhooks

To enable webhooks, create an integration and give the service account the necessary permissions.

To enable webhooks:

1. In the left navigation under *Integrations*, click **Integrations**.
2. Click the integration you want to enable with webhooks.
3. Find the *Webhooks* tab.
4. Click **Enable Webhooks**
5. If you have the required permissions, your repos or Git organizations will appear in a list in the *Webhooks* tab. Click **Install** for each integration you'd like to install the webhooks for.
  Use the dropdown menu to install webhooks for multiple repos or organizations at once.
6. When webhooks are enabled, the Installed column has a check mark.

## Troubleshooting

If you do not see any repos or organizations listed in the *Webhooks* tab of your integration, you may need to upgrade your permissions.

You will see a notification if a permissions adjustment is needed. Click **Update now** to adjust your permissions.

![Webhook provider permissions warning banner with the Update now button.](media://f825bc4f-ba3b-4678-8cd4-3fdfb705d971)

Depending on your Git host, the next steps may vary. In some cases you may need to request additional permissions from a Git host admin.

As an example, when setting up webhooks with GitHub, a pop-up appears asking you to authorize the connection and update permissions.

![GitHub additional permissions authorization modal with options to cancel or Authorize Git-Prime.](media://ee51240c-a23a-46bb-8a46-ff4943cbc21e)

You may need to make some adjustments within your Git host or to your personal access token before continuing to ensure all permissions and authorizations are correct. Once you have made those changes, click **Refresh all projects** for the specific integration you're looking at. After changing the permissions, navigate to the Webhooks tab to see what repos or organizations are available.