Use GitHub DevLog AI as a private, auditable inbox for your webhooks.
This guide covers daily use: configuring GitHub, validating signatures, understanding events, collaborating with your team, monitoring usage, and opening support requests.
What the product solves.
GitHub webhooks are powerful but hard to debug with only local logs, large payloads, and scattered responses. DevLog AI centralizes events in private workspaces, validates signatures, and turns each delivery into a readable timeline.
Private inbox
Each workspace has its own endpoint and Secret. One developer cannot see another workspace’s webhooks.
Validated signature
GitHub events are accepted with X-Hub-Signature-256 and a sanitized payload.
Collaboration
Developers, admins, and viewers can work with distinct roles without sharing a password or Secret.
From GitHub to the first received event.
Create or access a workspace
Open the dashboard and confirm that you are in the correct workspace. It shows your role, plan, monthly usage, and subscription status.
Copy the Payload URL and Secret
In GitHub settings, copy the private endpoint and workspace Secret. Only owners and admins can rotate the Secret.
Configure GitHub
In the repository, open Settings → Webhooks → Add webhook, select application/json, and paste the URL and Secret.
Choose events
Start with push and pull_request. Then add issues, workflow_run, or other events for your integration.
Send a ping
GitHub sends a ping event when the webhook is created. When it arrives, the dashboard shows the Delivery ID, repository, and payload.
Investigate in the dashboard
Open an event to inspect its signature, source, action, commits, changed files, notes, tasks, and sanitized raw payload.
When to use a manual webhook and when to use a GitHub App.
Manual webhook
Best for quickly testing one repository. Copy the URL and Secret, configure GitHub, and inspect events immediately.
GitHub App
Best for ongoing use, teams, and organizations. The app enables controlled installation and routing by an installation linked to the workspace.
Collaboration without sharing credentials.
Owner
Manages billing, team, Secrets, GitHub App, tests, and investigation.
Admin
Operates the workspace and manages members, billing, Secrets, and the GitHub App.
Developer
Investigates events and creates tests, notes, and tasks without changing billing or Secrets.
Viewer
Follows events and can contact support, but cannot perform sensitive actions.
Turn a payload into a diagnosis.
{
"event_name": "push",
"repository": "acme/api",
"delivery_id": "8189e9a8...",
"signature": "valid",
"branch": "main",
"commits": 3
}Control consumption before missing events.
Monthly limit
Each plan defines a monthly event allowance. The dashboard shows usage and preventative alerts.
Retention
Older events follow the plan retention policy, helping control cost and privacy.
Cancellation
Owners and admins can cancel the subscription in the dashboard. The action is audited and recorded.
If something does not work, start here.
Webhook did not arrive
Confirm that the URL is public, GitHub received HTTP 200, the endpoint is correct, and the monthly limit has not been reached.
Invalid signature
Check that the Secret in GitHub exactly matches the workspace Secret. If needed, rotate it and send a new ping.
Event looks incomplete
Verify that GitHub sends application/json and that the selected event includes the expected fields.
Billing or plan
Review the subscription center, Mercado Pago reference, and notifications. If something does not match, open a request with the reference.
Open a request with enough technical context.
Include repository, Delivery ID, approximate time, GitHub event, configured URL, GitHub or Mercado Pago HTTP response, and expected result. This reduces back-and-forth and speeds resolution.