Do I need API keys to use pushover-automation?

No API keys are needed — just add the MCP endpoint and rely on RUBE_SEARCH_TOOLS to fetch current schemas.

What if the tool slugs change?

Always search first with RUBE_SEARCH_TOOLS to fetch the latest tool slugs and input schemas; do not hardcode slugs.

Is memory required in every execute call?

Yes; include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty.

pushover-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/pushover-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Pushover Automation via Rube MCP

Automate Pushover operations through Composio's Pushover toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/pushover

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Pushover connection via RUBE_MANAGE_CONNECTIONS with toolkit pushover
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit pushover
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Pushover operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Pushover task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["pushover"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Pushover-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `pushover`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/pushover-automation/SKILL.mdView on GitHub

Overview

Automate Pushover operations using Composio's Pushover toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before workflows, establishing an ACTIVE Pushover connection, and executing tools in a memory-aware session for reliable notifications.

How This Skill Works

Rube MCP handles discovery, connections, and tool execution for Pushover. First, discover available tools with RUBE_SEARCH_TOOLS to get current slugs and input schemas; next, ensure the Pushover connection is ACTIVE via RUBE_MANAGE_CONNECTIONS; finally, run the chosen tool with RUBE_MULTI_EXECUTE_TOOL using a memory object and the session_id.

When to Use It

Automating Pus hover alerts from system events.
Ensuring you always fetch current tool schemas before a workflow.
Verifying the Pushover connection is ACTIVE prior to execution.
Executing a discovered Pushover tool with exact field names and memory as per the search results.
Reusing session IDs within a workflow and handling pagination when fetching tool data.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit pushover and ensure the connection is ACTIVE (follow the auth link if needed).
Step 3: Discover tools with RUBE_SEARCH_TOOLS for Pushover operations and execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Do not hardcode slugs or arguments; rely on the latest schemas.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs for a workflow and handle pagination as needed.

Example Use Cases

Discover a tool slug from search results (TOOL_SLUG_FROM_SEARCH) and send a Pushover alert with a message payload.
Connect to Pushover via RUBE_MANAGE_CONNECTIONS and execute TOOL_SLUG_FROM_SEARCH to notify multiple recipients.
Run a status-check tool after sending a notification to confirm delivery.
Set up an incident alert workflow that triggers a Pushover notification using a discovered tool slug.
Batch multiple Pushover notifications by reusing a single session across several TOOL_SLUG_FROM_SEARCH executions.

Frequently Asked Questions

Add this skill to your agents