Pushbullet Automation

What This Skill Does

This skill automates Pushbullet operations using the Composio Pushbullet toolkit via Rube MCP. It allows users to streamline Pushbullet workflows by discovering available tools, managing connections, and executing tasks. This is useful for anyone needing to automate Pushbullet tasks.

When to Use

Automate Pushbullet notification workflows. Check Pushbullet connection status. Discover available Pushbullet tools. Execute specific Pushbullet tasks. Integrate Pushbullet with other systems. Manage Pushbullet connections.

Key Features

Uses Rube MCP to automate Pushbullet. Discovers available tools via RUBE_SEARCH_TOOLS. Manages connections via RUBE_MANAGE_CONNECTIONS. Executes tools via RUBE_MULTI_EXECUTE_TOOL. Provides toolkit documentation link. Requires active Pushbullet connection.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedPushbullet Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pushbullet

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Pushbullet connection via RUBE_MANAGE_CONNECTIONS with toolkit pushbullet 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 pushbullet 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: "Pushbullet 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 Pushbullet task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["pushbullet"] 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

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

Toolkit docs: composio.dev/toolkits/pushbullet