What are the prerequisites to use this skill?

RUBE MCP must be connected, RUBE_SEARCH_TOOLS must be available, and the Fillout toolkit must be connected via RUBE_MANAGE_CONNECTIONS.

Do I need API keys for Fillout automation?

No API keys are required. Add the MCP endpoint and complete any authentication flow shown by the tool; the workflow handles further steps.

How should I handle changes in tool schemas?

Always run RUBE_SEARCH_TOOLS to fetch current schemas before executing tools, and do not hardcode tool slugs or argument names; adapt your workflow to the latest schema.

fillout-forms-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Fillout Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fillout_forms

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["fillout_forms"]
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 Fillout-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms`
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/fillout-forms-automation/SKILL.md

View on GitHub

Overview

Automate Fillout operations using Composio's Fillout toolkit through Rube MCP. Always search for current schemas with RUBE_SEARCH_TOOLS before running workflows to stay aligned with tool updates. This streamlines discovery, connection checks, and tool execution for form-fill tasks.

How This Skill Works

The workflow first discovers available Fillout tools with RUBE_SEARCH_TOOLS, then verifies the Fillout connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the required arguments from the discovered schema and a memory payload.

When to Use It

You need to automate form fillouts that use evolving schemas and must stay synced with the latest tool definitions.
bulk submissions are required across multiple forms or records from a CRM or data source.
you want to validate and run specific Fillout tasks only after confirming an active connection.
multi-step form workflows require memory to persist data across steps within a session.
you need to audit or compare tool schemas before execution to adapt to schema changes.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["fillout_forms"] and confirm the connection is ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload.

Best Practices

Always run RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool slugs and schemas.
Verify the RUBE_MANAGE_CONNECTIONS status is ACTIVE for the fillout_forms toolkit before running tools.
Use exact field names and types as returned by the tool schemas; avoid hardcoding slugs or parameters.
Include a memory payload in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Reuse session IDs within a workflow and handle pagination tokens when listed in responses.

Example Use Cases

Auto-fill a new customer form using the latest 'New Customer' tool slug derived from RUBE_SEARCH_TOOLS.
Bulk-submit 1,000 lead capture forms by iterating through discovered tools and their schemas.
Update address fields across a multi-step onboarding form, maintaining a single session for consistency.
Validate tool schemas by listing available tools with RUBE_SEARCH_TOOLS and verifying schemaRef presence.
Recover from a failed run by starting a new session_id while reusing existing memory to resume the workflow.

Frequently Asked Questions

Add this skill to your agents