Do I need API keys to use getform-automation?

No API keys are required. Add the MCP endpoint (https://rube.app/mcp) and use Rube MCP to manage connections and tool execution.

How do I ensure tool schemas stay up to date?

Always run RUBE_SEARCH_TOOLS before executing any Getform tool to fetch current tool slugs and input schemas.

What should I do if the connection shows not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup and retry until the status becomes ACTIVE.

getform-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Getform Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/getform

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Getform operations through Composio's Getform toolkit using Rube MCP. Always search for current tool schemas before running workflows to stay aligned with live definitions.

How This Skill Works

Connect to the Rube MCP and use RUBE_SEARCH_TOOLS to discover available Getform tools and their schemas. Establish an active Getform connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory object. Always ensure tool schemas are current and avoid hardcoding slugs or inputs; rely on the live search results for arguments.

When to Use It

When starting a Getform workflow, to discover available operations with up-to-date schemas
When verifying that the Getform toolkit connection is ACTIVE before running workflows
When selecting and executing a specific Getform tool using exact inputs from the current schema
When performing bulk or repetitive Getform tasks across multiple forms in a single session
When handling potential schema changes and needing to refresh tool slugs and inputs from RUBE_SEARCH_TOOLS

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify MCP is available by running RUBE_SEARCH_TOOLS and inspecting results
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["getform"] and ensure the session is ACTIVE before executing tools

Best Practices

Always search for current tool schemas before any execution
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to tool runs
Use exact field names and types from the live search results; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and fetch pagination tokens as needed

Example Use Cases

Auto-submit a Getform entry and route the data to a CRM by discovering the appropriate Getform tool, then executing it with live input fields.
Process a batch of Getform submissions from a daily export by iterating tool executions based on current schemas.
Route forms to different teams automatically based on a submission field (e.g., department) using live tool slugs.
Re-run a failed Getform operation by reusing the original session and correcting inputs without starting a new workflow.
Regularly refresh tool schemas with RUBE_SEARCH_TOOLS to adapt to schema changes and revalidate tool slugs.

Frequently Asked Questions

Add this skill to your agents