Get the FREE Ultimate OpenClaw Setup Guide →

formdesk-automation

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-skills/formdesk-automation --openclaw
Files (1)
SKILL.md
2.9 KB

Formdesk Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/formdesk

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Formdesk connection via RUBE_MANAGE_CONNECTIONS with toolkit formdesk
  • 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit formdesk
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Formdesk 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 Formdesk task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["formdesk"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Formdesk-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit formdesk
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/formdesk-automation/SKILL.mdView on GitHub

Overview

This skill automates Formdesk operations using Composio's Formdesk toolkit through Rube MCP. It requires an active Rube MCP connection and a Formdesk connection, and it emphasizes discovering current tool schemas before execution to avoid hardcoded slugs or fields.

How This Skill Works

Technical flow: first, call RUBE_SEARCH_TOOLS to discover available Formdesk tools and their input schemas. Next, verify the Formdesk connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory (even if empty) and the session_id from discovery, using the exact schema field names from the search results.

When to Use It

  • You need to automate repetitive Formdesk tasks (e.g., auto-submitting forms or bulk updates).
  • Tool schemas may change; you must fetch current schemas before calling tools.
  • You want to verify the Formdesk connection is ACTIVE before workflows.
  • Chaining multiple Formdesk actions in a single session using discovered tools.
  • Perform bulk or batch Formdesk operations using run_composio_tool workflows.

Quick Start

  1. Step 1: Ensure MCP is available and RUBE_SEARCH_TOOLS responds for Formdesk.
  2. Step 2: Manage Connection for toolkit 'formdesk' and confirm ACTIVE.
  3. Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it using RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

  • Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
  • Check RUBE_MANAGE_CONNECTIONS shows ACTIVE status before execution.
  • Use exact field names/types from the discovered schemas.
  • Include memory parameter in RUBE_MULTI_EXECUTE_TOOL calls (even when empty).
  • Reuse session IDs within a workflow; generate new ones only for new workflows.

Example Use Cases

  • Auto-submit a 'New Client Intake' Formdesk form when a lead is ready.
  • Create multiple Formdesk submissions from a dataset using discovered tools.
  • Refresh tool schemas after Formdesk field changes to avoid failures.
  • Chain discovery, connection check, and execution in a single workflow for onboarding.
  • Bulk update existing Formdesk records using RUBE_REMOTE_WORKBENCH with run_composio_tool.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers