What is RUBE MCP and how does it relate to Textit automation?

RUBE MCP is the Composio control plane used to manage connections and run Textit tools via the 'textit' toolkit; you connect, discover, and execute tools through its commands.

Why should I always call RUBE_SEARCH_TOOLS first?

To fetch current tool slugs and schemas because tool schemas change and hardcoding can break workflows.

What must be included in memory during multi tool execution?

Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls even if empty to satisfy the API and enable session continuity.

textit-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Textit Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/textit

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Textit operations through Composio's Rube MCP toolkit. It emphasizes discovering available Textit tools with RUBE_SEARCH_TOOLS to stay aligned with current schemas, then ensures an ACTIVE connection, and finally executes tools via RUBE_MULTI_EXECUTE_TOOL. This approach reduces manual setup and adapts to tool updates.

How This Skill Works

Prerequisites include a connected Rube MCP with RUBE_SEARCH_TOOLS and an ACTIVE Textit connection via RUBE_MANAGE_CONNECTIONS. The workflow is: discover tools with RUBE_SEARCH_TOOLS, verify the connection, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and schema-compliant arguments, including memory.

When to Use It

Automating recurring Textit messaging campaigns and responses.
Adapting to schema changes by re-discovering tool schemas before running workflows.
Coordinating multi-step Textit tasks in a single session.
Running bulk Textit operations across multiple tools.
Ensuring the Textit connection is ACTIVE before executing workflows.

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Textit operations"}], session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["textit"], session_id: "your_session_id"
Step 3: RUBE_MULTI_EXECUTE_TOOL with discovered tool_slug and memory: {} and session_id: "your_session_id"

Best Practices

Always run RUBE_SEARCH_TOOLS before executing to get current schemas.
Check RUBE_MANAGE_CONNECTIONS status and ensure ACTIVE.
Use exact field names and types from the tool schemas.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate a new one for new workflows.

Example Use Cases

Welcome automation: discover and execute a welcome tool for new Textit contacts.
Bulk messaging: run multiple Textit tasks in a single session across a campaign.
Schema changes: update an existing Textit workflow by re-discovering tool schemas before executing.
New workflow bootstrap: verify connection and start a session before running tools.
Result capture: log tool results in memory for downstream steps.

Frequently Asked Questions

Add this skill to your agents