pushover-notify

What This Skill Does

The pushover-notify skill enables OpenClaw to bridge the gap between agent automation and your mobile device. By integrating with the Pushover API, OpenClaw can push real-time, reliable notifications directly to your phone. Whether you need an urgent alert when a long-running process fails, a periodic heartbeat check to confirm your server is still online, or a simple reminder to perform a task, this skill provides a robust notification channel that works independently of your current interface. It supports advanced features like customizable sound profiles, specific device routing, and emergency priority levels that require manual acknowledgment.

Installation

To integrate this skill, ensure you have the OpenClaw environment initialized. Execute the installation command: clawhub install openclaw/skills/skills/digitallyborn/pushover-notify. After installation, configure your environment variables by setting PUSHOVER_APP_TOKEN and PUSHOVER_USER_KEY within your secure credential manager. Do not store these keys directly in the script or any shared configuration files. Once keys are configured, the skill is ready for invocation via the command-line interface or triggered automatically through agent workflows.

Use Cases

This skill is ideal for "out-of-band" alerts. Primary use cases include:

1. Long-running task completion: Receive a notification when a heavy data scrape or compilation process finishes.
2. System Health Monitoring: Configure cron jobs to ping the Pushover API if a service stops responding or disk usage exceeds a defined threshold.
3. Reminders: Use OpenClaw as a personal assistant to push scheduled reminders about meetings or errands throughout the day.
4. Critical Incident Escalation: Use priority 2 messages for urgent server errors that require immediate human intervention.

Example Prompts

1. "OpenClaw, when the script in the terminal finishes, send me a Pushover notification letting me know the result."
2. "Please set a reminder for 5 PM to check the market data and send it as a notification to my phone."
3. "If the server monitor reports a downtime event, trigger an emergency Pushover alert to my device immediately."

Tips & Limitations

• Rate Limiting: Be mindful of Pushover's message limits for your account to avoid service suspension.
• Priority Management: Use priority levels judiciously. Do not use priority 2 (emergency) for routine alerts, as it ignores notification silence settings on many devices.
• Automation Integration: Always pair this with cron for repetitive tasks rather than using a long-running polling loop, as cron is more resource-efficient for scheduled notifications.
• Security: Treat your APP_TOKEN as a password. If the token is exposed, rotate it via the Pushover dashboard immediately.