What are GitHub webhooks?
GitHub webhooks send an HTTP request when an event occurs in your GitHub account. Teams use them to react to repository activity, pull requests, and issue changes without repeatedly polling an API. Hookflo gives each delivery a searchable record and can notify the right team when an event arrives or signature verification fails.
Events to monitor
Choose the event types that matter in your GitHub configuration. Common examples include:
- push
- pull_request
- issues
Connect GitHub to Slack or email
- Create a webhook in Hookflo and select GitHub.
- Copy the unique Hookflo webhook URL.
- In Repository or organization Settings → Webhooks, add the Hookflo URL and choose the event types to send.
- Use the webhook secret configured in GitHub. GitHub signs deliveries with HMAC-SHA256 and sends the signature in X-Hub-Signature-256.
- Save the endpoint, send a test event, and choose Slack or email for notifications.
Verify signatures and debug delivery issues
Check that the webhook secret in Hookflo matches the secret saved on the GitHub webhook, and that GitHub is sending JSON.
When a delivery fails, check the selected event, destination URL, and provider-specific signing secret first. Hookflo keeps the event payload and verification result together so the issue is easier to diagnose.
Read GitHub webhook documentationCan I get Slack alerts for GitHub webhook events?
Yes. Send GitHub deliveries to a Hookflo endpoint, configure the same webhook secret in Hookflo, and route the events to a Slack channel.