GitHub Webhooks Integration

Test and debug GitHub repository events, pull requests, and CI/CD pipeline webhooks

Step 1: Create a Webhook Endpoint
Generate your unique webhook URL in WebhookDebugger
  1. Sign in to your WebhookDebugger account
  2. Click "Create Endpoint" in your dashboard
  3. Name it "GitHub - MyRepo" or similar
  4. Copy your unique webhook URL
Step 2: Add Webhook to GitHub
Configure GitHub to send events to your WebhookDebugger URL
  1. Go to your GitHub repository
  2. Click Settings → Webhooks → Add webhook
  3. Paste your WebhookDebugger URL in the "Payload URL" field
  4. Set Content type to "application/json"
  5. Choose which events to trigger the webhook:
    • "Just the push event" (simplest)
    • "Send me everything" (for testing)
    • "Let me select individual events" (recommended for production)
  6. Leave "Active" checked
  7. Click "Add webhook"
Step 3: Test Your Webhook
Trigger an event in GitHub to see the webhook

After creating the webhook, GitHub automatically sends a ping event. Check WebhookDebugger to see it!

To test other events:

  • Make a commit to trigger push event
  • Create a PR to trigger pull_request event
  • Add a star to trigger star event
  • Create an issue to trigger issues event
Common GitHub Webhook Events
  • push- Code pushed to repository
  • pull_request- PR opened, closed, or updated
  • issues- Issue created or modified
  • issue_comment- Comment on issue or PR
  • release- Release published
  • star- Repository starred
  • fork- Repository forked
  • workflow_run- GitHub Actions workflow completed
💡 Pro Tips

• GitHub webhooks include an X-Hub-Signature-256 header for verification

• You can view webhook delivery history in GitHub Settings → Webhooks → Recent Deliveries

• Use the X-GitHub-Event header to identify the event type

• GitHub automatically retries failed webhook deliveries up to 3 times

• Perfect for testing CI/CD pipelines before deploying to production