GitHub Webhook Payload Transformer
GitHub webhooks push events — push, pull request, issue, release, and more — as JSON to your server whenever activity occurs in a repository or organization.
Example Payload — push
{
"ref": "refs/heads/main",
"repository": {
"name": "my-app",
"full_name": "acme-org/my-app",
"private": false
},
"commits": [
{
"id": "abc1234def5678",
"message": "fix: resolve null pointer in auth middleware",
"author": {
"name": "Jane Dev",
"email": "jane@example.com"
}
}
],
"pusher": {
"name": "jane-dev"
}
}Best Output Formats
Deployment trigger payload
extract branch, commit SHA, and repo name for your CI/CD system
Slack notification format
format commits list into a readable message block
Audit log entry
flatten pusher, ref, and commit count into a single database row
Common Use Cases
Trigger deployments automatically when commits land on the main branch
Post commit summaries to a Slack channel for team visibility
Index commit messages for searchable changelogs and release notes
Ready to transform your GitHub webhooks?
Open Webhook Transformer →FAQ
What does a GitHub webhook payload look like?
GitHub webhooks push events — push, pull request, issue, release, and more — as JSON to your server whenever activity occurs in a repository or organization. A typical "push" event includes fields for deployment trigger payload.
How do I transform GitHub webhook payloads?
Use the Aarunya Webhook Transformer to paste your GitHub payload and select your desired output format. Common formats include: Deployment trigger payload, Slack notification format, Audit log entry.
What are the best uses for GitHub webhooks?
Trigger deployments automatically when commits land on the main branch Post commit summaries to a Slack channel for team visibility Index commit messages for searchable changelogs and release notes