Do I need API keys for Formcarry automation?

No API keys are required. You configure the MCP server at https://rube.app/mcp and use RUBE_SEARCH_TOOLS and related commands to manage tools.

What if the tool schema changes after discovery?

Always fetch updated schemas using RUBE_SEARCH_TOOLS before executing to ensure your arguments match the current schema.

How should I handle sessions across multiple steps?

Reuse a single session_id within a workflow for related actions and generate new session_ids for independent workflows to avoid conflicts.

formcarry-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Formcarry Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/formcarry

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Formcarry operations through Composio's Formcarry toolkit via Rube MCP. The workflow centers on discovering current tool schemas with RUBE_SEARCH_TOOLS and ensuring an ACTIVE Formcarry connection before running any tasks.

How This Skill Works

Connect Rube MCP and verify that RUBE_SEARCH_TOOLS returns tool schemas. Discover available Formcarry tools for a given use case, then check that the Formcarry connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and memory payload.

When to Use It

When you need end-to-end automation of a Formcarry task from tool discovery to execution.
When switching between different Formcarry tasks and you must fetch updated schemas first.
When validating that the Formcarry connection is ACTIVE before running workflows.
When reusing a session across multiple Formcarry operations to optimize flow control.
When handling paginated tool discovery results and iterating through all available tools.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and confirm RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS with a Formcarry use_case to discover available tool slugs and input schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit 'formcarry' to activate the connection, then use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug, arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to fetch current tool schemas.
Verify the Formcarry connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones only for new workflows.

Example Use Cases

Example 1: Discover a Formcarry task with RUBE_SEARCH_TOOLS, select TOOL_SLUG_FROM_SEARCH, and run it with RUBE_MULTI_EXECUTE_TOOL in a single session.
Example 2: Automate multiple related Formcarry submissions by reusing a session_id across steps and ensuring the memory payload is passed consistently.
Example 3: Validate the Formcarry connection status before batch executing several tools in a single workflow.
Example 4: Iterate through all available Formcarry tools retrieved from RUBE_SEARCH_TOOLS and execute them sequentially with proper memory management.
Example 5: Handle a form update by re-discovering tool schemas and adjusting arguments without hardcoding slugs.

Frequently Asked Questions

Add this skill to your agents