A webhook is a custom callback over HTTP used to setup communication between applications. They provide a way to automatically notify other applications when an event has occurred in your application in the form of an HTTP post payload. This eliminates the need to poll your application to check for new events – the application will alert you when there's something new! Webhooks in FlexDeploy can be used to trigger actions in FlexDeploy based on events happening in other applications, thus eliminating some manual actions. For example, you can setup a webhook to build a project immediately after a push occurs in your SCM. This is just one example, and FlexDeploy's model offers flexibility in what you can accomplish with webhooks.
Overview
Webhooks can be accessed from Administration → Integrations → Webhooks. This page will show all the webhook functions configured in FlexDeploy. Each function contains a Groovy script which will be executed whenever an event is received at the listed URI from the configured provider. Webhook Providers can be accessed from the 
button on the functions page. Click 
to view the results of any received webhooks, or to resubmit them.
See more details about each webhook topic below:
Common issues/FAQ
findProjectsForChange/findPackagesForChange isnt finding my projects
- The most common reason your projects/packages are not being found is the Webhooks Enabled flag is not checked on the project
- Ensure the repository name configured in your integration instance in FlexDeploy matches the repository name received from the webhook (case insensitive).
- If a sparse checkout folder is configured on your project your project will only be detected for a change if one of the modified files from the push event is contained in the sparse checkout folder
- For example - If you received a push event for a changed file /content/project1/dist/index.html. A project with sparse checkout 'content/project2' would not be returned whereas a project with sparse checkout 'content/project1' would be
How do I create a new Release Snapshot from a webhook build?
- The simplest way is to simply configure a Snapshot Schedule on your release. When the schedule runs it will find the newly built project version which resulted from the webhook.
- A function also exists 'createSnapshot' which can be used within a webhook function.
No webhooks are being received by FlexDeploy (webhook messages screen is blank)
The webhooks may not be getting through because of the firewall. See Webhook Security for options on allowing webhooks to be received by FlexDeploy without sacrificing security.
Should I manage webhooks per repository, or globally for my SCM?
Webhooks in FlexDeploy have the capability for both options. Most SCMs have separate configuration of webhooks per repository. If you don't need separate customizations per repository, it's recommended to create one provider and one or a couple functions in FlexDeploy for your SCM for easier management. However, if your use case is different depending on the repository, you can configure multiple providers for your SCM to group repositories, or group them by URIs associated with different functions, and manage them separately in that way.
What if I don't see a function that I need?
If there is a function that you don't see available that would be needed to fit your use case you can first check the release notes of later FlexDeploy versions to see if the function you need has since been added. If you still don't see your function you can open an enhancement request on the support site.