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

SKILL

flowiseai-automation

Name: flowiseai-automation
Author: Composio

Automate FlowiseAI tasks via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears primarily to be an instructional prompt and does not directly require local installation, secrets, or a fixed remote endpoint. However, it is designed to route actions through Rube MCP/Composio to connect and execute Flowiseai tools, so practical use still involves external service connectivity and remote tool execution; overall this is low-to-moderate risk with caution points.

CredentialsCaution

The material says “No API keys needed,” but it also requires creating an active `flowiseai` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which indicates likely third-party OAuth/account authorization in practice. There is no explicit request to paste raw secrets; the credential risk mainly comes from external connection authorization rather than the skill itself.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and references Composio docs. In practice, `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL` likely send user task parameters and session data to Rube/Composio and the connected Flowiseai service. There is network egress, but the endpoints and purpose are aligned with the stated functionality, with no clear red flag of unrelated exfiltration.

Code executionLow risk

Based on the provided material, this skill is a prompt/workflow guide and does not include local script installation, shell commands, package-manager steps, or direct requests for system execution privileges. It instructs use of remote MCP tools, but there is no evidence here of spawning local processes or executing arbitrary code on the host.

Data accessCaution

The documentation does not claim direct access to local files or system data, so there is no sign of excessive local data access. However, the skill is intended to “Automate Flowiseai operations” through remote tool execution, meaning business data, session IDs, and tool arguments supplied by the user may be processed by remote services. The effective data access scope depends on the connected Flowiseai/Composio tool permissions, so inputs should be minimized.

Supply chainLow risk

This item is system-labeled as prompt-only and comes from a GitHub open-source repository with strong community adoption (~64.7k stars), both of which significantly lower risk. Although the license is unspecified and maintenance status is unknown, and the referenced Rube/Composio services are not fully auditable from this material alone, the skill material itself has relatively good auditability and source credibility.

Recommendations

Only complete the authorization flow after confirming you trust Rube/Composio and the connected Flowiseai account; prefer least-privilege accounts.
Do not place unnecessary sensitive data in tool arguments, memory, or sessions; verify the remote service’s data-handling boundaries first.
Before first use, review Rube MCP and Composio privacy policies, connection scopes, and log-retention details.
If your environment has stricter requirements, validate in an isolated test account what tools and data fields `RUBE_MULTI_EXECUTE_TOOL` actually invokes.

Audited by: gpt-5.4 · 2026-06-17

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Bubble tasks via Rube MCP using the latest tool schemas.

ComposioGet→

$ loading_