notifications
Pushover CLI for Headless Automation
Use the Pushover CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.
3 functions 2 read 1 write API key auth
Pushover CLI for Headless Automation
Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.
Use headless automation when another tool needs a stable local command surface. The Pushover CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Pushover CLI for Headless Automation
kosmokrator integrations:configure pushover --set api_key="$PUSHOVER_API_KEY" --set user_key="$PUSHOVER_USER_KEY" --enable --read allow --write ask --json
kosmo integrations:call pushover.pushover_send_message '{"message":"example_message","title":"example_title","priority":1,"url":"example_url","url_title":"example_url_title","sound":"example_sound","device":"example_device","timestamp":1}' --json Discovery Before Execution
Agents and scripts can inspect Pushover docs and schemas before choosing a function.
kosmo integrations:docs pushover --json
kosmo integrations:docs pushover.pushover_send_message --json
kosmo integrations:schema pushover.pushover_send_message --json
kosmo integrations:search "Pushover" --json
kosmo integrations:list --json Useful Pushover CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
pushover.pushover_send_message | Write | message, title, priority, url, url_title, sound, device, timestamp, expire, retry | Send a push notification via Pushover. Supports message, title, priority levels, and optional URL/sound attachments. |
pushover.pushover_list_sounds | Read | none | List available notification sounds in Pushover. Use sound names with the send_message tool. |
pushover.pushover_get_current_user | Read | none | Validate the Pushover user credentials and retrieve account information. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.