formsite-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/formsite-automation --openclawFormsite Automation via Rube MCP
Automate Formsite operations through Composio's Formsite toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/formsite
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Formsite connection via
RUBE_MANAGE_CONNECTIONSwith toolkitformsite - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitformsite - 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: "Formsite 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 Formsite task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["formsite"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Formsite-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit formsite |
| 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/formsite-automation/SKILL.mdView on GitHub Overview
Automate Formsite operations through Composio's Formsite toolkit via Rube MCP. It enables repeatable Formsite workflows by discovering current tool schemas before execution and validating the active connection. Keeping schemas fresh and connections healthy reduces errors and maintenance.
How This Skill Works
The skill uses RUBE_SEARCH_TOOLS to fetch available Formsite tools for a given use case, then verifies an ACTIVE connection with RUBE_MANAGE_CONNECTIONS. It then executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id, always referencing the latest schemas to avoid hard-coded slugs or parameters.
When to Use It
- Automate a specific Formsite operation by discovering its tool slug and required fields via RUBE_SEARCH_TOOLS.
- Verify and maintain an ACTIVE Formsite connection before executing any workflows.
- Fetch up-to-date tool schemas before integrating or updating automation to avoid hard-coded slugs.
- Execute sequential or bulk Formsite tasks within a single session, reusing session_id for consistency.
- Handle tool responses with pagination tokens when listing many tools or schemas.
Quick Start
- Step 1: Discover Available Tools - RUBE_SEARCH_TOOLS with queries: [{use_case: "your specific Formsite task"}] and session: {id: "existing_session_id"}
- Step 2: Check Connection - RUBE_MANAGE_CONNECTIONS with toolkits: ["formsite"] and session_id: "your_session_id"
- Step 3: Execute Tools - RUBE_MULTI_EXECUTE_TOOL with tools: [{tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args from search results */}}], memory: {}, session_id: "your_session_id"
Best Practices
- Always call RUBE_SEARCH_TOOLS first to retrieve current tool schemas.
- Check RUBE_MANAGE_CONNECTIONS for ACTIVE status before executing tools.
- Use exact field names and types from the search results to ensure schema compliance.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and paginate through results as needed.
Example Use Cases
- Discover tools for a Formsite task (e.g., CreateSubmission), then execute with provided form field values.
- Fetch the latest Formsite tool schemas and adapt your arguments before running a tool.
- Validate the active Formsite connection, then run multiple tools in a single session to process several submissions.
- Handle large tool lists by paging through results until complete.
- Bulk update multiple forms by reusing a session and executing corresponding tools one after another.
