Do I need API keys to use Insighto AI automation?

No API keys are required; just add the MCP server at https://rube.app/mcp and follow the setup steps.

Why must I call RUBE_SEARCH_TOOLS before running tools?

Tool schemas change frequently; to avoid hardcoding slugs or arguments, always fetch current schemas.

What should memory contain in RUBE_MULTI_EXECUTE_TOOL calls?

Include memory as an object, even if empty, to preserve context between tool executions.

insighto-ai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Insighto AI Automation via Rube MCP

Automate Insighto AI operations through Composio's Insighto AI toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/insighto_ai

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["insighto_ai"]
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 Insighto AI-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `insighto_ai`
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/insighto-ai-automation/SKILL.md

View on GitHub

Overview

Automate Insighto AI operations through Composio's Insighto AI toolkit using Rube MCP. Always fetch current tool schemas first via RUBE_SEARCH_TOOLS, then establish a connection with insighto_ai and execute tools.

How This Skill Works

Discover tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Ensure an ACTIVE connection using RUBE_MANAGE_CONNECTIONS for the insighto_ai toolkit. Execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing memory and session_id, and rely on live schemas rather than hardcoding.

When to Use It

When you need up-to-date Insighto AI tool schemas before workflow execution.
When automating recurring Insighto AI tasks with a managed MCP connection.
When orchestrating multi-tool Insighto AI workflows and tracking sessions.
When validating tool slugs and arguments against live schemas instead of hardcoding.
When performing bulk or parallel tool executions via RUBE_MULTI_EXECUTE_TOOL.

Quick Start

Step 1: Discover available tools with RUBE_SEARCH_TOOLS
Step 2: Check connection with RUBE_MANAGE_CONNECTIONS
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
Use exact field names/types from the search results; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination if present.

Example Use Cases

Automating a data prep and analysis flow by discovering tools, verifying connection, then executing a chosen Insighto AI tool.
Orchestrating a nightly Insighto AI evaluation pipeline that fetches current schemas and uses RUBE_MULTI_EXECUTE_TOOL.
Bulk-running multiple Insighto AI endpoints as part of a batch processing job via RUBE_REMOTE_WORKBENCH.
Diagnosing schema changes by re-searching tools before each workflow run.
Setting up an automated Insighto AI task that requires live input schemas and authenticated sessions.

Frequently Asked Questions

Add this skill to your agents