Webhooks

Incoming webhooks notify our servers to make something. Outgoing webhooks make another service to do something when events happen with your sites.

Incoming webhooks

The only supported action for incoming webhooks right now is to trigger new builds and deploys.

You can find your incoming webhooks settings in the site page, right under the build environment settings.

Set an appropriate tile that describes how the hook will be triggered, for instance “Daily Cron Hook” and save it.
Netlify will give you a unique URL for that webhook. To trigger this hook, just send a POST request to that URL.

GitHub commit statuses

It requires a GitHub access token with at least the repo:status scope.
GitHub tokens are bounded to users, so creating several tokens doesn’t change their API limit restrictions. Each usage accumulates to the user limit per hour.

You can generate an access token directly from Netlify when you configure this notification:

GitHub pull request comments

This webhook adds a comment notification in your GitHub Pull Requests. It also updates that same comment if you append several commits to the same pull request.

It requires a GitHub access token with public_repo or repo scope, depending on whether your repository is public or private.
GitHub tokens are bounded to users, so creating several tokens doesn’t change their API limit restrictions. Each usage accumulates to the user limit per hour.

You can generate an access token directly from Netlify when you configure this notification:

GitLab commit statuses

This webhook creates commit statuses in your GitLab repositories.

It requires a GitLab API token with access to the repository.
You can set that token when you configure this notification:

GitLab merge request comments

This webhook adds a comment notification in your GitLab merge requests. It also updates that same comment if you append several commits to the same merge request.

It requires a GitLab API token with access to the repository.
You can set that token when you configure this notification:

Bitbucket commit statuses

This webhook creates commit statuses in your Bitbucket repositories.

It requires a Bitbucket app password and a username.
You can set those fields when you configure this notification:

Bitbucket pull request comments

This webhook adds a comment notification in your Bitbucket pull requests. It also updates that same comment if you append several commits to the same pull request.

It requires a Bitbucket app password and a username.
You can set those fields when you configure this notification:

Notice something is incorrect or outdated?

First off, great eye! We appreciate your discovery and want to ensure it gets addressed immediately. Please let us know here.