Pushover

SKILL.md

---
name: oo-pushover
description: "Pushover (pushover.net). Use this skill for ANY Pushover request — reading, creating, updating, and deleting data. Whenever a task involves Pushover, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
  title: "Pushover"
  author: "OOMOL"
  version: "1.0.0"
  service: "pushover"
  categories: "Communication"
  homepage: "https://pushover.net"
  icon: "https://static.oomol.com/logo/third-party/Pushover.svg"
---

# Pushover

Operate **Pushover** through your OOMOL-connected account. This skill calls the `pushover` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Communication. Exposes 29 action(s).

## Running an action

Assume the user has already installed the oo CLI, signed in, and connected Pushover. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.

**1. Inspect the contract** to get the authoritative input/output schema before building a payload:

```bash
oo connector schema "pushover" --action "<action_name>"
```

**2. Run the action** with a JSON payload that matches the input schema:

```bash
oo connector run "pushover" --action "<action_name>" --data '<json>' --json
```

- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.

Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.

## Available actions

- [`ack_delete_messages_up_to_id`](actions/ack_delete_messages_up_to_id.md) — Acknowledge and delete all Open Client messages up to the provided message identifier.
- [`add_group_user`](actions/add_group_user.md) — Add an existing Pushover user to a delivery group.
- [`add_team_user`](actions/add_team_user.md) — Add a user to a Pushover for Teams organization using the Team API token.
- [`assign_license`](actions/assign_license.md) — Assign one prepaid Pushover license credit to a user by key or email address.
- [`cancel_receipt_retries`](actions/cancel_receipt_retries.md) — Cancel further retries for one emergency receipt before it expires.
- [`cancel_retries_by_tag`](actions/cancel_retries_by_tag.md) — Cancel retries for all active emergency receipts that share the provided tag.
- [`check_license_credits`](actions/check_license_credits.md) — Get the number of prepaid Pushover license credits remaining on the application.
- [`client_login`](actions/client_login.md) — Authenticate an Open Client user with email, password, and optional two-factor code.
- [`create_group`](actions/create_group.md) — Create a new Pushover delivery group.
- [`disable_group_user`](actions/disable_group_user.md) — Temporarily disable deliveries to a user, or one of the user's devices, inside a delivery group.
- [`enable_group_user`](actions/enable_group_user.md) — Re-enable deliveries to a previously disabled user, or one of the user's devices, inside a delivery group.
- [`fetch_client_messages`](actions/fetch_client_messages.md) — Download pending Open Client messages for a registered device.
- [`get_app_icon_image`](actions/get_app_icon_image.md) — Download a Pushover application icon PNG by icon identifier and return its binary content as base64.
- [`get_app_limits`](actions/get_app_limits.md) — Get the current monthly message limit, remaining messages, and reset time for the connected Pushover application.
- [`get_app_token`](actions/get_app_token.md) — Return the application API token resolved from the action input or the connected credential.
- [`get_group`](actions/get_group.md) — Get the name and membership of a Pushover delivery group.
- [`get_receipt_status`](actions/get_receipt_status.md) — Get the status of an emergency notification receipt, including acknowledgment, callback, and expiry details.
- [`get_team_api_token`](actions/get_team_api_token.md) — Return the Team API token resolved from the action input or the connected credential metadata.
- [`list_groups`](actions/list_groups.md) — List the delivery groups owned by the connected Pushover application account.
- [`listen_client_websocket`](actions/listen_client_websocket.md) — Open a temporary Open Client WebSocket session, login with the provided device and secret, and collect realtime events until timeout or close.
- [`register_client_device`](actions/register_client_device.md) — Register an Open Client desktop device using a user session secret.
- [`remove_group_user`](actions/remove_group_user.md) — Remove a user, or one of the user's devices, from a delivery group.
- [`remove_team_user`](actions/remove_team_user.md) — Remove a user from a Pushover for Teams organization without deleting the user's Pushover account.
- [`rename_group`](actions/rename_group.md) — Rename an existing Pushover delivery group.
- [`send_message`](actions/send_message.md) — Send a Pushover notification to a user or delivery group, with optional emergency settings, URL metadata, and image attachment.
- [`store_team_api_token`](actions/store_team_api_token.md) — Validate a Pushover Team API token for later use. Persist the token through the provider connection extra field when needed.
- [`subscription_flow`](actions/subscription_flow.md) — Validate and echo a Pushover subscription code collected through the web subscription flow.
- [`update_glances`](actions/update_glances.md) — Update Pushover Glances widget data for a user without creating a push notification.
- [`validate_user_or_group`](actions/validate_user_or_group.md) — Validate that a Pushover user or delivery group key can receive notifications, optionally restricted to one device.

## Safety

- Read actions (get / list / search) are safe to run directly.
- **Create, update, send, or post actions change Pushover state — confirm the exact payload and effect with the user before running.**
- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**

## First-time setup

These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):

  ```bash
  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  ```

  ```powershell
  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  ```

- **Not signed in / authentication error** — sign in to your OOMOL account once:

  ```bash
  oo auth login
  ```

- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Pushover is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  ```text
  https://console.oomol.com/app-connections?provider=pushover
  ```

- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

## Resources

- Pushover homepage: https://pushover.net