GitHub events as push notifications

Route 1: the repo webhook (pushes, releases, stars, issues)

1. Create an endpoint in the Webhooky app (Android / iOS) – e.g. “GitHub” with the notification_2 sound and a default text like “Activity in my repo”.
2. In your repository: Settings → Webhooks → Add webhook. Payload URL = your endpoint, content type application/json, then pick the events (just the push event, or “Let me select individual events” for releases, stars, issues …).

GitHub's payloads are event-specific JSON without title/message fields, so the push shows your endpoint's configured texts – you hear that something happened and see which repo, the details are on GitHub. One endpoint per repo (each with its own color) keeps things sorted.

Route 2: CI alerts from GitHub Actions – with real texts

For “the build is red” you want the error in the notification, not a generic text. Add a final step to your workflow:

  - name: Notify on failure
    if: failure()
    run: |
      curl -X POST https://api.webhooky.app/YOUR_KEY \
        -H "Content-Type: application/json" \
        -d '{"title":"🚨 CI failed: ${{ github.repository }}","message":"${{ github.workflow }} on ${{ github.ref_name }}","sound":"error_1"}'

Store the endpoint URL as a repository secret if the repo is public. A matching if: success() step with level_up_2 makes green builds audible too.

Which route when?

Webhook for ambient awareness (stars, releases, pushes by teammates), Actions step for CI results with exact texts. Both together cost nothing – the free plan's 100 notifications cover a lot of pushes. GitLab user? Same guide for GitLab.

Get Webhooky

Free for your first 100 notifications – set up your endpoint in two minutes.