Use cases · GitHub

GitHub events, without refreshing the repo.

Add Hook as a webhook on a repository or an organisation. Pushes, pull requests, releases and workflow runs arrive as notifications labelled GitHub, with the full event to read.

  • Recognised as GitHub, with the event type kept in the headers
  • Topics keep repositories apart in the app and the web app
  • Mute a noisy topic, or notify only from a priority up, without losing events
  • 60 requests a minute per workspace covers busy repositories
Hook's inbox with a GitHub push next to other senders

Set it up in a minute. Three steps.

  1. Step 1

    Copy your endpoint

    Add a topic per repository, for example /github-api.

  2. Step 2

    Add the webhook

    In the repository, open Settings → Webhooks → Add webhook. Paste the URL, choose application/json and select the events.

  3. Step 3

    Get the push

    GitHub sends a ping first, then every selected event arrives as a notification.

Payload URL
https://gethook.app/workspace/{workspace_key}/github-api

Replace {workspace_key} with the key shown in the app. Fields like title and priority are explained in Publishing messages.

What people ask before they set it up.

Does Hook check the X-Hub-Signature-256 header?

No. It keeps the header with the request so you can see it, but it does not verify it.

Can I use it for GitHub Actions too?

Yes. A workflow step can call your endpoint with curl and set its own title and priority. See the CI notifications use case.

Compared with other tools for this job.

More uses for Hook.

Get the next request on your phone. Free to start.