$ ~/registry/skill/composiohq-composio-skills-scrapfly-automation

SKILL

scrapfly-automation

Automate Scrapfly workflows through Rube MCP with tool discovery and execution.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "scrapfly-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/scrapfly-automation/SKILL.md
2. Save it as ~/.claude/skills/scrapfly-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Safely call Scrapfly tools in a workflow

Developers use it in automation flows to discover tools, verify schemas, and then execute Scrapfly operations, reducing failures caused by interface changes.

Manage connection and execution in one flow

Before running a task, users can verify that the scrapfly connection is active and then proceed, avoiding interruptions caused by incomplete authorization.

Build reusable MCP automation flows

Teams can reuse session IDs, follow recommended execution plans, and fetch full schemas when needed for more reliable Scrapfly automation integrations.

// docs

AI summary

The documentation explains how to automate Scrapfly tasks through Rube MCP using Composio's Scrapfly toolkit. It covers prerequisites, connection setup, tool discovery, and the standard execution pattern. A key point is to always call RUBE_SEARCH_TOOLS first to get the latest schemas, then verify the scrapfly connection is ACTIVE, and only then execute tools with RUBE_MULTI_EXECUTE_TOOL while handling memory, session reuse, pagination, and full schema lookup when needed.

Show full docs ▾

Scrapfly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/scrapfly

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["scrapfly"]
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 Scrapfly-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `scrapfly`
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

// FAQ

What does this skill do?

It lets you automate Scrapfly-related tasks through Rube MCP using Composio's Scrapfly toolkit. The docs specifically emphasize searching for tools first and then executing with the current schema.

What prerequisites are required?

You need Rube MCP connected and RUBE_SEARCH_TOOLS available. You also need a scrapfly toolkit connection configured through RUBE_MANAGE_CONNECTIONS and confirmed as ACTIVE.

Why must I search for tools every time first?

Because tool schemas may change, the docs explicitly say not to hardcode tool slugs or arguments. You should call RUBE_SEARCH_TOOLS first to get the current tools, input schemas, and execution guidance.

Automate AppsFlyer queries, reports, and attribution tasks through Rube MCP.

ComposioGet→

$ loading_