Icypeas Automation

What This Skill Does

This skill automates Icypeas operations using Composio's Icypeas toolkit via Rube MCP. It enables users to programmatically interact with Icypeas features, streamlining workflows and integrations. This is beneficial for those seeking to automate repetitive tasks or connect Icypeas with other systems.

When to Use

• Automate data analysis tasks.
• Create custom reports programmatically.
• Integrate Icypeas with data visualization tools.
• Automate data cleaning and transformation.
• Build custom data pipelines.
• Schedule automated data backups.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Icypeas connection.
• Discovers available tools and schemas dynamically.
• Provides a core workflow pattern for tool execution.
• Emphasizes the importance of schema compliance.
• Manages connections via RUBE_MANAGE_CONNECTIONS.

Manual Installation

Manual installation

• View Full Skill Content.
• The complete markdown content that gets installed.
• Icypeas Automation via Rube MCP.

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

Toolkit docs: composio.dev/toolkits/icypeas

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["icypeas"] 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 Icypeas operations through Composio's Icypeas toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/icypeas