Textit Automation

What This Skill Does

This skill automates Textit operations through Composio's Textit toolkit via Rube MCP. It enables users to discover available tools, check connections, and execute specific Textit tasks, simplifying workflows for SMS marketing and communication.

When to Use

• Automate SMS campaigns.
• Send personalized text messages.
• Manage contact lists via SMS.
• Set up automated SMS replies.
• Integrate SMS with other systems.
• Trigger workflows based on SMS input.

Key Features

• Uses Rube MCP for Textit automation.
• Discovers tools via RUBE_SEARCH_TOOLS.
• Manages connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Provides toolkit documentation link.
• Requires active Textit connection.

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