Formbricks Automation
This skill automates Formbricks operations using Composio's Formbricks toolkit via Rube MCP. It's designed for users who need to streamline form management and
Install
npx promptshop add formbricks-automationDetails
What This Skill Does
- This skill automates Formbricks operations using Composio's Formbricks toolkit via Rube MCP.
- It's designed for users who need to streamline form management and data handling within Formbricks.
- The skill ensures proper setup, tool discovery, and execution while avoiding common pitfalls.
When to Use
Automate form submission processingUpdate form configurationsRetrieve form dataTrigger actions based on form responsesManage user access to formsIntegrate form data with other systems
Key Features
- Uses Rube MCP for Formbricks automation.
- Requires an active Formbricks connection.
- Employs RUBE_SEARCH_TOOLS for tool discovery.
- Checks connection status via RUBE_MANAGE_CONNECTIONS.
- Executes tools using RUBE_MULTI_EXECUTE_TOOL.
- Provides guidance on avoiding common pitfalls.
Formbricks 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_CONNECTIONS with toolkit formbricks 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 formbricks 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_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 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 |
Automate Formbricks operations through Composio's Formbricks toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/formbricks