Get Cloudflare Workers build notifications on your phone via Pushover. This Worker consumes build events from a Cloudflare Queue and forwards them as push notifications with appropriate priority, sound, and direct links to the Cloudflare dashboard.

Screenshot

Features

• 🔔 Real-time push notifications for build success, failure, and cancellation
• 🚨 Failed builds sent with high priority (bypasses quiet hours) and siren sound
• 🔗 Direct link to the build in the Cloudflare dashboard
• 📋 Build details: worker name, branch, commit, author, duration
• 🔒 Only two secrets to configure — no hardcoded values

How It Works

┌─────────────────┐     ┌──────────────────────────┐     ┌──────────────────┐     ┌──────────┐
│ Workers Builds  │────▶│ Cloudflare Queue          │────▶│ This Worker      │────▶│ Pushover │
│ (any worker in  │     │ (event subscription)      │     │ (queue consumer) │     │ → Phone  │
│  your account)  │     │                            │     │                  │     │          │
└─────────────────┘     └──────────────────────────┘     └──────────────────┘     └──────────┘

1. Any Worker in your Cloudflare account triggers a build
2. Workers Builds publishes an event to your Cloudflare Queue via Event Subscriptions
3. This consumer Worker formats the event and sends it to the Pushover API
4. Pushover delivers the notification to your phone

Notification Examples

Setup

Prerequisites

• A Pushover account with the app installed on at least one device (iOS, Android, or Desktop)
• A Cloudflare account with Workers enabled

Step 1: Create a Pushover Application

1. Go to pushover.net/apps/build
2. Name it (e.g., "Cloudflare Builds") and optionally upload an icon
3. Copy the API Token/Key (30 characters)

Step 2: Note Your Pushover User Key

1. Go to your Pushover dashboard
2. Copy your User Key (30 characters)

Step 3: Deploy the Worker

Click the button below to deploy via the Cloudflare dashboard:

Or deploy manually:

git clone https://github.com/sslboard/pushover-cloudflare-build-notifications.git
cd pushover-cloudflare-build-notifications
npm install
wrangler deploy

Step 4: Create the Queue

Important: The queue must exist before the worker can consume from it.

wrangler queues create builds-event-subscriptions

Or via the Cloudflare Dashboard → Create Queue → name it builds-event-subscriptions.

Step 5: Set Secrets

wrangler secret put PUSHOVER_APP_TOKEN
# Paste your Pushover application API token

wrangler secret put PUSHOVER_USER_KEY
# Paste your Pushover user key

Or via the Cloudflare Dashboard → Workers → your worker → Settings → Variables and Secrets.

Step 6: Create the Event Subscription

Subscribe your queue to Workers Builds events so that builds emit events into your queue:

wrangler queues subscription create builds-event-subscriptions \
  --source workersBuilds.worker \
  --events build.succeeded,build.failed \
  --worker-name pushover-build-notifications

Or via the Cloudflare Dashboard → Queues → your queue → Subscriptions tab → Subscribe to events → source: Workers Builds → select events → Subscribe.

Step 7: Test It!

Push a commit to any Worker in your account that has Workers Builds enabled. You should receive a Pushover notification on your phone within seconds.

Event Types

Event Schema

Workers Builds events follow this structure (see Cloudflare docs):

{
  "type": "cf.workersBuilds.worker.build.succeeded",
  "source": {
    "type": "workersBuilds.worker",
    "workerName": "my-worker"
  },
  "payload": {
    "buildUuid": "build-12345678-90ab-cdef-1234-567890abcdef",
    "status": "success",
    "buildOutcome": "success",
    "createdAt": "2025-05-01T02:48:57.132Z",
    "stoppedAt": "2025-05-01T02:50:15.132Z",
    "buildTriggerMetadata": {
      "buildTriggerSource": "push_event",
      "branch": "main",
      "commitHash": "abc123def456",
      "commitMessage": "Fix bug in authentication",
      "author": "developer@example.com",
      "repoName": "my-worker-repo",
      "providerAccountName": "github-user",
      "providerType": "github"
    }
  },
  "metadata": {
    "accountId": "your-account-id",
    "eventSubscriptionId": "sub-1234",
    "eventSchemaVersion": 1,
    "eventTimestamp": "2025-05-01T02:48:57.132Z"
  }
}

Configuration

Secrets

Queue Settings (wrangler.jsonc)

Development

# Install dependencies
npm install

# Generate types (do NOT install @cloudflare/workers-types)
npx wrangler types

# Run tests
npm test

# Run tests in watch mode
npm run test:watch

# Local development
npm run dev

# View live logs
npm run tail

Troubleshooting

No notifications appearing

1. Check the queue — Dashboard → Queues → your queue. Are messages arriving?
2. Check worker logs — Dashboard → Workers → your worker → Logs
3. Verify subscription — Queues → your queue → Subscriptions tab
4. Verify secrets — Workers → your worker → Settings → Variables and Secrets

Deploy fails with "Queue does not exist"

Create the queue first (see Step 4).

Pushover returns "invalid token"

• Verify PUSHOVER_APP_TOKEN is the application token from pushover.net/apps, not your user key
• Verify PUSHOVER_USER_KEY is from your dashboard

Build events not appearing in the queue

• Ensure you have Workers Builds enabled on at least one worker
• Ensure the event subscription includes the event types you expect (at minimum build.succeeded and build.failed)

Learn More

• Pushover Message API
• Cloudflare Queue Event Subscriptions
• Workers Builds
• Workers Builds Event Schema
• Cloudflare Queues

License

MIT