Relay

Cel mai simplu mod de a-ți conecta serviciile la PushWard. Direcționează webhook-uri către relay.pushward.app — fără containere Docker, fără găzduire proprie, fără configurare per utilizator.

Supported Providers

Grafana notification ArgoCD steps Radarr steps Sonarr steps Prowlarr notification Jellyfin generic Changedetection.io alert Proxmox VE steps Overseerr / Seerr steps Uptime Kuma alert Gatus alert Backrest steps Bazarr notification Paperless-ngx generic Unmanic generic Gitea steps Forgejo generic Komodo alert TrueNAS alert

Grafana

POST /grafana

notification

Info Configurare

Evenimente

• Firing
• Resolved (grouped by alertname)

Public Relay

PushWard hosts a public relay at relay.pushward.app — no deployment required. Just point your services at it with your integration key.

# Grafana Contact Point URL:
https://relay.pushward.app/grafana

# HTTP Header:
Authorization: Bearer hlk_YOUR_INTEGRATION_KEY

How It Works

pushward-relay extracts the hlk_ integration key from each incoming webhook request. The relay infrastructure scales horizontally — one instance can serve many users concurrently. Per-user usage is bounded by your account's plan (free tier monthly quotas; unlimited on paid).

1. Receive — external services send webhooks to provider-specific routes
2. Authenticate — the integration key is extracted from the Authorization: Bearer hlk_... header (or Basic Auth password for Radarr/Sonarr/Prowlarr/Bazarr/Komodo, or GenieKey for TrueNAS)
3. Transform — the provider handler maps the webhook payload to a push notification or Live Activity update depending on the event type
4. Forward — the request is sent to PushWard using the caller's integration key

Push Notifications vs Live Activities

Each provider delivers events as either a push notification (banner alert) or a Live Activity (Dynamic Island + Lock Screen), depending on the event type:

poster:
  enabled: true
  allow_private_hosts: true

Per-request overrides

Append query parameters to any provider webhook URL to override that provider's delivery behavior for a single request. This is handy when one source should behave differently from the provider default — for example forcing a noisy alert to a plain notification, or bumping a deploy's priority. An explicit parameter always wins over the provider-computed value and your static config; omitting a parameter leaves today's behavior unchanged.

https://relay.pushward.app/grafana?channels=notification&level=time-sensitive

Setup

1. Get Your Integration Key

Copiază cheia ta de integrare implicită din aplicația PushWard din Settings → Integration Key; este creată automat când te autentifici. Pentru a restrânge o cheie la această integrare, vezi crearea cheilor cu domeniu restrâns.

2. Self-Hosted (Optional)

If you prefer to run your own relay instance:

services:
  pushward-relay:
    image: ghcr.io/mac-lucky/pushward-relay:latest
    ports:
      - "8090:8090"
    environment:
      PUSHWARD_URL: https://api.pushward.app
      PUSHWARD_DATABASE_DSN: postgres://user:pass@db:5432/relay?sslmode=disable
    restart: unless-stopped

  db:
    image: postgres:17-alpine
    environment:
      POSTGRES_USER: user
      POSTGRES_PASSWORD: pass
      POSTGRES_DB: relay
    volumes:
      - relay-data:/var/lib/postgresql/data

volumes:
  relay-data:

Authentication

Three patterns depending on the provider:

Configuration

Each provider can be individually enabled/disabled and configured with its own priority, cleanup delay, and stale timeout via environment variables or YAML config.