Docs / Vendor onboarding

Connect GitHub webhooks to Relin

Use this when GitHub repository or organization events drive deploys, issue automation, CI work, or customer workflows. Relin receives GitHub webhooks, verifies the HMAC signature, records every delivery, and lets you replay safely after your own endpoint is fixed.

Open Relin workspace Open GitHub webhooks

What you need

Relin access

Owner or admin access to the Relin workspace where events should land.

GitHub access

Admin access to the GitHub account or app where you configure webhooks.

Test event

A safe GitHub test event or development account you can use before production traffic.

1. Create the GitHub source in Relin

  1. In Relin, open Developer → Inbound.
  2. Click Add source.
  3. Select the GitHub tile.
  4. Name the source, for example GitHub production.
  5. Save the source and copy the ingest URL. You will paste this URL into GitHub.
Relin source picker with GitHub selected
Select GitHub from the source picker, then name the source after the repository or organization sending events.

2. Configure GitHub

  1. Open the repository or organization settings in GitHub.
  2. Go to Webhooks and click Add webhook.
  3. Paste the Relin ingest URL into Payload URL.
  4. Set Content type to application/json.
  5. Enter a webhook secret. You will paste the same value into Relin.
  6. Choose the events your product depends on, then save the webhook.

Recommended GitHub events

Repository automation

push
pull_request
workflow_run
deployment_status

Issue workflows

issues
issue_comment
label
milestone

3. Copy the GitHub webhook secret into Relin

  1. Use the same secret value in GitHub and Relin.
  2. Return to the Relin source settings page.
  3. Paste the secret into Signing secret.
  4. Save the source.
Relin source created panel for GitHub
After the source is created, copy the ingest URL before leaving the page. The token is shown once.

4. Send a test event

  1. Open the webhook in GitHub.
  2. Use Recent deliveries to redeliver the ping event, or trigger a subscribed event such as a push.
  3. Open Relin Events and confirm the newest GitHub event has signature status verified.

GitHub notes

  • Relin verifies GitHub's X-Hub-Signature-256 header. Prefer that over older SHA-1 signatures.
  • Organization webhooks can be noisy. Subscribe only to events you actually route or monitor.

Troubleshooting

  • No event in Relin: confirm the Payload URL exactly matches the Relin ingest URL.
  • Signature failed: update either GitHub or Relin so both use the same secret value.
  • Events arrive but your app does not update: inspect the Relin delivery attempt for the downstream response body and status.

Official references

Next