Never Miss a GitHub Actions Failure: Instant Alerts with Echobell

Email and Slack notifications for CI failures are easy to miss. The Echobell Notification Action sends webhook alerts straight to your phone—push notifications for normal builds, phone calls for production failures—so broken pipelines don't go unnoticed.

Setup

1. Create an Echobell Channel

1. Download Echobell and sign in
2. Create a channel named something like "GitHub CI/CD Alerts"
3. Copy the webhook URL from channel settings
4. In your GitHub repo: Settings → Secrets and variables → Actions → New repository secret
5. Name it ECHOBELL_WEBHOOK_URL, paste the URL

2. Add to Your Workflow

Basic setup (single-job workflows):

name: Build and Test

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v4

      - name: Build
        run: npm run build

      - name: Test
        run: npm test

      - name: Notify on Failure
        if: failure()
        uses: weelone/echobell-action@v1
        with:
          webhook-url: ${{ secrets.ECHOBELL_WEBHOOK_URL }}

Multi-job pipelines — use a dedicated notification job that depends on all critical jobs:

name: Deploy Pipeline

on:
  push:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run Tests
        run: npm test

  build:
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Build
        run: npm run build

  deploy:
    needs: build
    runs-on: ubuntu-latest
    steps:
      - name: Deploy
        run: ./deploy.sh

  notify_on_failure:
    runs-on: ubuntu-latest
    needs: [test, build, deploy]
    if: failure()
    steps:
      - name: Send Failure Notification
        uses: weelone/echobell-action@v1
        with:
          webhook-url: ${{ secrets.ECHOBELL_WEBHOOK_URL }}

The dedicated notification job gives you one consolidated alert for cascading failures rather than multiple separate notifications.

Tips

Notification titles should answer: what failed, where, and when. Use patterns like ❌ Main Branch CI Failed or 🚨 Deploy Pipeline Down - Production.

Use separate channels per severity. Keep a standard channel for normal CI alerts and a second channel set to Calling for production failures. Point different workflows to different webhook URLs. See call notifications for details.

Share channels with your team. Create a channel for CI/CD failures the whole team should see, and a separate one for infra-only issues. Echobell's shared channels let teammates subscribe with their own notification preferences—no need for everyone to configure webhooks individually.

Related

• Webhook docs — full webhook API reference
• Templates and Conditions — customize notification content and filtering
• Grafana call notifications — phone call alerts for monitoring systems
• WebhookMCP notifications — alerts for AI task completion
• Feature docs: Channels, Webhooks, Email triggers, Call notifications