Do I need API keys to use tapform-automation?

No API keys are required. Add the MCP endpoint (https://rube.app/mcp) and ensure RUBE_SEARCH_TOOLS is available, then connect to the Tapform toolkit.

What if tool slugs change?

Always search tools first with RUBE_SEARCH_TOOLS; avoid hardcoding slugs or argument names.

Is memory required for executions?

Yes. Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

tapform-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Tapform Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/tapform

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Tapform operations using Composio's Tapform toolkit through Rube MCP. It emphasizes discovering current tool schemas before execution and ensures connections are ACTIVE, so workflows stay aligned with live tool definitions.

How This Skill Works

The workflow uses RUBE_SEARCH_TOOLS to fetch current Tapform tool schemas, then RUBE_MANAGE_CONNECTIONS to verify an ACTIVE connection. It then executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required memory and session details based on the latest schema.

When to Use It

Automating recurring Tapform tasks with up-to-date tool schemas
Setting up and verifying a Tapform connection via Rube MCP
Running a discovered tool slug with correct arguments
Ensuring memory and session handling in multi-tool execution
Handling tool schema changes or pagination in tool discovery

Quick Start

Step 1: Connect to Rube MCP and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover available Tapform tools with RUBE_SEARCH_TOOLS and pick a tool slug
Step 3: Check connection and execute the tool with memory using RUBE_MULTI_EXECUTE_TOOL

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing
Use exact field names and types from the search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Submit a new Tapform form by discovering the 'submit_form' tool slug and executing with mapped fields
Update an existing Tapform record by discovering 'update_record' and providing exact schema fields
Bulk-create multiple Tapform records after confirming an ACTIVE connection via Rube MCP
Fetch latest tool schemas mid-workflow to adapt to changes without hardcoding slugs
Handle paginated tool lists by iterating through RUBE_SEARCH_TOOLS results until complete

Frequently Asked Questions

Add this skill to your agents