8.0
/ 10
1 evaluations
2.4k Downloads
Overview
Send push notifications to Pushover (pushover.net) from OpenClaw workflows via a Node.js script that wraps the Pushover API.
Key Advantages
1.Simple, focused integration for out-of-band push notifications with minimal setup in OpenClaw.
2.Relies on Pushover’s infrastructure for reliable push delivery across devices (iOS, Android, desktop).
3.Supports Pushover features like title, message, priority levels (-1 to 2), emergency retry/expire, device targeting, URL and URL title, and custom sounds.
4.Credentials are passed via environment variables instead of being hardcoded in the skill, reducing secret-exposure risk.
5.Works well as a building block for alerting/notification patterns (cron-based reminders, monitoring alerts, workflow completion notices).
Use Cases
- Send critical monitoring or error alerts from OpenClaw workflows to a phone when jobs fail or services degrade.
- Create cron-based reminders and heartbeat checks that notify you if a job stops running or misses a schedule.
- Notify on completion of long-running tasks, data pipelines, or deployments so you don’t need to poll for status.
- Escalate emergency conditions (priority 2 with retry/expire) for incidents like “service down” or “security anomaly detected.”
- Send concise ‘notify me when X happens’ alerts for event triggers, thresholds, or anomaly detections in other OpenClaw skills.
Evaluation Scores
8.0
/ 10
Reliability
8.0
Functionality
7.5
Usability
7.0
Safety
8.5
Performance
9.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/20/2026
Download Trend
Loading...
Evaluation History (1)
8.0/103/20/2026▼
OS: linux-arm64LLM: z-ai/glm-4.5-air
**Quick judgement:** A solid, focused notification skill that cleanly exposes Pushover’s push API to OpenClaw. It’s well-suited as an alerting primitive ("tell me when X happens"), with good reliability derived from Pushover and a straightforward Node.js wrapper.
**What it does well**
- Sends push notifications with title, body, priority, URL, sound, and device selection.
- Supports emergency (priority 2) messages with `--retry` and `--expire`, which is important for high-severity alerts.
- Uses environment variables (`PUSHOVER_APP_TOKEN`, `PUSHOVER_USER_KEY`, optional device/sound) rather than hardcoding secrets, which is a safer pattern.
- Plays nicely with cron and other OpenClaw skills to form robust alerting and reminder workflows.
**Main risks / limitations**
- **External dependency:** Delivery depends entirely on Pushover’s availability and your device’s connectivity; if Pushover is down or rate-limited, alerts may be delayed or lost.
- **No built-in queueing or retries (beyond Pushover emergency):** The script appears to make a direct API call; if it fails (network/HTTP error), you’ll need outer logic (cron, retries) to ensure delivery.
- **Privacy and data handling:** All notification content goes through Pushover’s service. Sensitive data in messages is subject to Pushover’s handling and device lock-screen exposure.
- **User setup burden:** Requires manual creation of a Pushover app token and user key, and correct env var configuration. Non-technical users may need guidance.
**Recommended scenarios**
- Reliable out-of-band alerts for monitoring, error conditions, or job failures where immediate human attention is desired.
- Cron-based reminders and heartbeat checks (e.g., "alert me if this cron doesn’t run" or "daily summary at 9am").
- Notifications on completion or failure of long-running or background OpenClaw workflows.
- Incident and on-call style alerts where priority and emergency retry semantics are important.
For teams already using Pushover and comfortable with environment variable configuration, this skill is a practical and reasonably safe choice for integrating push alerts into OpenClaw automations.
Comments (0)
No comments yet. Be the first!