formbricks-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/formbricks-automation --openclawFormbricks Automation via Rube MCP
Automate Formbricks operations through Composio's Formbricks toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/formbricks
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Formbricks connection via
RUBE_MANAGE_CONNECTIONSwith toolkitformbricks - 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 toolkitformbricks - 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: "Formbricks 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 Formbricks task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["formbricks"]
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 Formbricks-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit formbricks |
| 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/formbricks-automation/SKILL.mdView on GitHub Overview
Automate Formbricks operations through Composio's Formbricks toolkit via Rube MCP. This skill guides you to discover current tool schemas, verify a live Formbricks connection, and execute tools within a robust workflow. By emphasizing up-to-date schemas and ACTIVE connections, you can build reliable Formbricks automations.
How This Skill Works
Begin by querying RUBE_SEARCH_TOOLS to fetch available Formbricks tool slugs and input schemas. Then establish or verify the Formbricks connection with RUBE_MANAGE_CONNECTIONS, ensuring the status is ACTIVE before running workflows. Finally, execute the selected tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, a memory payload, and a session ID.
When to Use It
- When automating Formbricks tasks through Rube MCP and you need up to date tool schemas.
- When setting up a new Formbricks workflow and you must validate an ACTIVE connection first.
- When you want to avoid hardcoding tool slugs by discovering tools at runtime.
- When performing multi-step operations requiring session management and memory payloads.
- When troubleshooting, using known pitfalls like pagination and schema compliance.
Quick Start
- Step 1: Add the Rube MCP server at https://rube.app/mcp in your client configuration and verify RUBE_SEARCH_TOOLS is available.
- Step 2: Use RUBE_MANAGE_CONNECTIONS to connect the formbricks toolkit and confirm ACTIVE status.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then run a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from search results; do not hardcode slugs.
- Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL, even if empty.
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Discover the Formbricks tool slugs with RUBE_SEARCH_TOOLS and execute a tool with RUBE_MULTI_EXECUTE_TOOL using the returned arguments.
- Set up the Formbricks connection via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before running a workflow.
- Run a multi-tool Formbricks operation by selecting a slug from search results and supplying the required arguments.
- Perform bulk operations with RUBE_REMOTE_WORKBENCH and run multiple Formbricks tools using run_composio_tool().
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before automation.
