What is Synthflow AI Automation via Rube MCP?

A workflow to automate Synthflow AI tasks by discovering tool schemas, managing connections, and executing tools through Rube MCP.

Why should I always search tools first?

Tool schemas change; searching ensures you use current slugs and input field types rather than risking outdated configurations.

What if the connection isn't ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check until ACTIVE before proceeding.

synthflow-ai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Synthflow AI Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/synthflow_ai

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["synthflow_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 Synthflow AI-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `synthflow_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/synthflow-ai-automation/SKILL.md

View on GitHub

Overview

Automate Synthflow AI operations through Composio's Synthflow AI toolkit via Rube MCP. It prioritizes discovering current tool schemas before execution to avoid hardcoding slugs or arguments. The setup requires Rube MCP connected and an active Synthflow AI connection using the synthflow_ai toolkit.

How This Skill Works

The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to fetch slugs and input schemas. Next, you verify the connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying exact arguments and a memory object, always referencing the fresh schemas from the search results.

When to Use It

Starting a new Synthflow AI task and needing the latest tool schemas
Verifying that the Rube MCP connection is ACTIVE before running workflows
Discovering tools for a specific Synthflow AI use case and then executing
Building multi-step workflows that reuse a session ID
Performing bulk or batch tool executions with RUBE_REMOTE_WORKBENCH or run_composio_tool

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds to confirm tooling availability
Step 2: Run RUBE_MANAGE_CONNECTIONS for the synthflow_ai toolkit and ensure status is ACTIVE
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination as needed

Example Use Cases

Automate a single Synthflow AI task by discovering the tool slug, verifying the ACTIVE connection, and executing with the appropriate arguments
Create a two-step workflow that runs Tool A followed by Tool B within the same session
Execute multiple tools in bulk using RUBE_REMOTE_WORKBENCH and run_composio_tool
Populate tool arguments dynamically from schemas returned by RUBE_SEARCH_TOOLS rather than hardcoding
Detect an INACTIVE connection, complete authentication via the provided link, then resume the workflow

Frequently Asked Questions

Add this skill to your agents