Browserless Automation

What This Skill Does

This skill automates Browserless operations through the Composio platform using Rube MCP. It enables programmatic interaction with Browserless's features. It's designed for developers and automation specialists who need to integrate Browserless into their automated workflows.

When to Use

• Automate browser tasks with Browserless
• Perform web scraping using Browserless
• Run automated browser tests
• Manage Browserless sessions
• Simulate user interactions on websites
• Integrate Browserless into automation flows

Key Features

• Leverages Rube MCP for tool discovery and execution
• Requires an active Browserless connection
• Offers a structured workflow for automation
• Highlights dynamic schema discovery
• Manages connections using RUBE_MANAGE_CONNECTIONS
• Executes tools via RUBE_MULTI_EXECUTE_TOOL

Prerequisites

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

Step 2: Check Connection

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

Powered by Composio