What is Flowiseai Automation via Rube MCP?

A method to automate Flowiseai tasks by discovering tool schemas with RUBE_SEARCH_TOOLS, validating an active Flowiseai connection, and executing tools through RUBE_MULTI_EXECUTE_TOOL within a session.

What are the prerequisites?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an Active Flowiseai connection via RUBE_MANAGE_CONNECTIONS with toolkit flowiseai; always search tools first for current schemas.

What should I do if tool schemas change?

Always re-run RUBE_SEARCH_TOOLS to fetch updated slugs and schemas before executing tools, and avoid hardcoding tool Slugs or arguments.

flowiseai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Flowiseai Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/flowiseai

Prerequisites

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

Step 2: Check Connection

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

Overview

Flowiseai Automation via Rube MCP lets you control Flowiseai operations using Composio's Rube MCP. It requires a connected Rube MCP and an Active Flowiseai connection, with a mandatory initial scan of tool schemas before execution. This keeps tool usage current and avoids hardcoding slugs or arguments.

How This Skill Works

You first discover available Flowiseai tools using RUBE_SEARCH_TOOLS, then verify the Flowiseai connection with RUBE_MANAGE_CONNECTIONS. Once confirmed, you execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id. This workflow emphasizes schema freshness and explicit validation before running any tool.

When to Use It

Setting up a new Flowiseai automation project and establishing initial connections
Automating repetitive Flowiseai tasks within a Composio workflow
Ensuring tool schemas are current by always performing RUBE_SEARCH_TOOLS before execution
Managing and validating Flowiseai connections (ACTIVE) across workflows
Orchestrating batch tool executions with memory and session management

Quick Start

Step 1: Add the Flowiseai toolkit to your Rube MCP and confirm RUBE_SEARCH_TOOLS is available
Step 2: Run RUBE_SEARCH_TOOLS with use_case set to Flowiseai operations to fetch current tool slugs and schemas
Step 3: Call RUBE_MANAGE_CONNECTIONS for the flowiseai toolkit and execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id

Best Practices

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

Example Use Cases

Automate a Flowiseai data-cleaning pipeline by discovering the required tool via RUBE_SEARCH_TOOLS and executing it with the discovered schema
Set up a Flowiseai integration in a project by establishing an ACTIVE RUBE_MANAGE_CONNECTIONS and proceeding through discovery and execution
Create a multi-step Flowiseai workflow that discovers tools, checks the connection, and executes tools using RUBE_MULTI_EXECUTE_TOOL with memory and session management
Regularly re-search Flowiseai tool schemas to pick up updated slugs and arguments before re-running a job
Perform bulk operations using RUBE_REMOTE_WORKBENCH to run multiple Flowiseai tools in a single batch

Frequently Asked Questions

Add this skill to your agents