Do I need API keys to use Parsehub automation?

No API keys are required for MCP; you just add the MCP endpoint and connect. Authentication is handled by the Rube MCP flow.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS first to fetch current schemas; do not hardcode tool slugs or fields.

How should I structure arguments?

Pass exact schema-compliant arguments from the search results and include memory in the multi-execute call.

parsehub-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Parsehub Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/parsehub

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["parsehub"]
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 Parsehub-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `parsehub`
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/parsehub-automation/SKILL.mdView on GitHub

Overview

Parsehub automation via Composio's Rube MCP toolkit enables automated Parsehub operations. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and requires an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. This keeps workflows resilient to schema changes and setup updates.

How This Skill Works

First, discover available Parsehub tools using RUBE_SEARCH_TOOLS to pull current input schemas and execution plans. Then verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS for the parsehub toolkit. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing memory and the schema-compliant arguments from the discovery results.

When to Use It

When you need to automate recurring Parsehub tasks instead of manual runs
When tool schemas change, to avoid hardcoding tool slugs or args
When preparing a Parsehub workflow that requires an ACTIVE connection
When integrating Parsehub operations into bulk or multi-tool workflows
When handling data extractions that require pagination or session reuse

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS is available and returns Parsehub tool slugs
Step 2: Connect using RUBE_MANAGE_CONNECTIONS with toolkit 'parsehub' and confirm ACTIVE
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before running any workflow to fetch current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE prior to execution
Use exact field names and types from search results; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new tasks; watch for pagination tokens

Example Use Cases

Automate a nightly product data scrape from a Parsehub project
Update a price monitoring dataset by triggering Parsehub via Rube MCP
Chain a discovery → connect → execute flow for a new provider site
Run bulk Parsehub extractions across multiple projects in a single workflow
Handle paginated results by repeatedly invoking tools until complete

Frequently Asked Questions

Add this skill to your agents