Getform Automation

What This Skill Does

• This skill automates operations within Getform using Composio's Getform toolkit via Rube MCP.
• It is designed for users who need to programmatically interact with Getform for tasks like managing forms and submissions.
• The skill requires an active Getform connection and Rube MCP setup.

When to Use

Create a new formRetrieve form submissionsUpdate form settingsAutomatically respond to submissionsIntegrate form data into other systemsMonitor form performance

Key Features

• Uses Rube MCP for automation.
• Requires active Getform connection.
• Discovers available tools via RUBE_SEARCH_TOOLS.
• Checks connection status via RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Provides setup and usage instructions.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedGetform 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.
• 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