Do I need API keys to use affinity-automation via Rube MCP?

No API keys needed — just add the endpoint https://rube.app/mcp as an MCP server in your client configuration.

What should I include in memory for RUBE_MULTI_EXECUTE_TOOL?

Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).

Why must I call RUBE_SEARCH_TOOLS before executing workflows?

Tool schemas change; never hardcode tool slugs or arguments. Call RUBE_SEARCH_TOOLS to fetch current schemas and recommended execution plans.

affinity-automation

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

Files (1)

SKILL.md

2.9 KB

Affinity Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/affinity

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Affinity tasks via Composio's Affinity toolkit using Rube MCP. The workflow relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and ensuring an ACTIVE Affinity connection before execution.

How This Skill Works

Step 1: Discover available tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. Step 2: Ensure an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the affinity toolkit. Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing memory and session_id as required by the discovered schema.

When to Use It

When you need up-to-date tool schemas before running any Affinity operation
When integrating Affinity workflows into larger automation pipelines
When you must verify and maintain an ACTIVE Rube MCP connection to Affinity
When you want to reuse a session_id across multiple steps in a workflow
When performing bulk or sequenced Affinity operations and need schema-driven arguments

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp to your client and verify availability with RUBE_SEARCH_TOOLS
Step 2: Manage the Affinity connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before running any tool
Check the connection status via RUBE_MANAGE_CONNECTIONS and ensure ACTIVE
Use exact field names and types from the tool schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty {})
Reuse session IDs within a workflow and fetch new ones for separate workflows

Example Use Cases

Automate updating Affinity labels across records by discovering a tool, connecting, then executing with specified args
Sync Affinity tasks with CRM records using a discovered tool slug and memory for state
Run a cleanup or audit tool after discovering schemas, ensuring an ACTIVE connection first
Perform bulk grouping of Affinity items by executing multiple tools in a single session
Adapt to schema changes by re-searching tools before each tool execution

Frequently Asked Questions

Add this skill to your agents