When configuring a webhook, you can choose which events will send you payloads. To limit the number of HTTP requests to your server, you should only subscribe to the specific events that you plan on handling. By default, webhooks installed on GitHub Enterprise, an [organization][org-hooks], or a [repository][repo-hooks] are only subscribed to the push event. By default, webhooks on GitHub Apps are not subscribed to any events. You can change events that a webhook is subscribed to at any time.
You can create webhooks that subscribe to the events listed on this page. Each webhook event includes a description of the webhook properties and an example payload. For more information, see "Creating webhooks."
Webhook payload object common properties
Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections.
| Key | Type | Description |
|---|---|---|
action | string | Most webhook payloads contain an action property that contains the specific activity that triggered the event. |
sender | object | The user that triggered the event. This property is included in every webhook payload. |
repository | object | The repository where the event occurred. Webhook payloads contain the repository property when the event occurs from activity in a repository. |
organization | object | Webhook payloads contain the organization object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization. |
installation | object | The GitHub App installation. Webhook payloads contain the installation property when the event is configured for and sent to a GitHub App. For more information, see "Registering a GitHub App." |
The unique properties for a webhook event are the same properties you'll find in the payload property when using the