Skip to main content

Point GitHub at your capture URL

1

Copy your capture URL

It is on Arrivals: https://in.webhooktrap.dev/c/ followed by a 12-character key.
2

Add the webhook

In the repository, open Settings › Webhooks › Add webhook. Set Payload URL to the capture URL, Content type to application/json, and set a secret.
3

Trigger events

Push a commit, open an issue, or use Redeliver on a recent delivery in the webhook’s settings.
Webhook Trap recognises a GitHub delivery by its X-GitHub-Event header, takes the event type from that header and the event id from X-GitHub-Delivery, and groups events by repository and organization.

Configure the agent

webhooktrap.yml
If you leave out secret, the agent looks for GITHUB_WEBHOOK_SECRET, the name in the GitHub pack.
Your signing secret stays on your machine. webhooktrap.yml holds only the name of the environment variable (secret: env:NAME). The agent reads the value when it signs a delivery, strips every known secret variable from the environment of probe and reset commands, and refuses to write or upload a run document that contains the secret. The server learns the variable’s name, never its value.
GitHub signs no timestamp, so the body and its original X-Hub-Signature-256 still verify later. Without the secret the agent sends valid deliveries with the captured signature header; with it, it re-signs them.

What the scenarios do for GitHub

The 10 s budget comes from GitHub’s docs. A budget: above it in webhooktrap.yml is refused as a configuration error, because it would hide a failure GitHub documents.