CI failures straight to your phone
A red pipeline you notice an hour later costs you the whole hour. Add one step to your workflow and failed builds ring your phone the moment they happen.
GitHub Actions: notify on failure
Add this as the last step of any job – it only fires when something before it failed:
- 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","message":"${{ github.repository }} · ${{ github.workflow }} · ${{ github.ref_name }}"}'Store the key as a repository secret (secrets.WEBHOOKY_KEY) if the repo is public. The same pattern works in GitLab CI (when: on_failure), CircleCI, Jenkins – anywhere you can run a shell command.
Repository webhooks
For events outside CI, use GitHub's built-in webhooks: repo Settings → Webhooks → Add webhook, paste your Webhooky link as payload URL, content type application/json, and select the events you care about – releases, issues, stars, pull requests. The notification shows your endpoint's configured text; details are in the stored payload if you enable store payload.
Deploys & releases
Add a POST at the end of your deploy script and give it a happy sound – hearing every successful production deploy is surprisingly reassuring:
curl -X POST "https://api.webhooky.app/DEPLOY_KEY" \
-H "Content-Type: application/json" \
-d '{"title":"🚀 Deployed","message":"v1.4.2 is live on production"}'
