supportbee-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/supportbee-automation --openclawSupportbee Automation via Rube MCP
Automate Supportbee operations through Composio's Supportbee toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/supportbee
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Supportbee connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsupportbee - 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 toolkitsupportbee - 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: "Supportbee 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 Supportbee task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["supportbee"]
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 Supportbee-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit supportbee |
| 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/supportbee-automation/SKILL.mdView on GitHub Overview
Automate Supportbee operations using Composio's Supportbee toolkit through the Rube MCP interface. The workflow emphasizes discovering up-to-date tool schemas with RUBE_SEARCH_TOOLS and establishing an active Supportbee connection via RUBE_MANAGE_CONNECTIONS before execution.
How This Skill Works
Start by discovering available tools with RUBE_SEARCH_TOOLS, filtering by a Supportbee use_case. Then verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing a memory payload and the session_id.
When to Use It
- Beginning a Supportbee workflow and need the latest tool schemas.
- You must establish or verify an active Supportbee connection before running tools.
- You want to run a specific Supportbee task discovered via RUBE_SEARCH_TOOLS.
- Coordinating multiple tool executions in a single session using RUBE_MULTI_EXECUTE_TOOL.
- Handling paginated tool results and ensuring schema changes are accounted for.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS with use_case set to 'Supportbee operations' to enumerate tools.
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'supportbee', then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using a valid session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
- Check that the Supportbee connection is ACTIVE before execution.
- Use exact field names and types as returned in the tool schemas.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls.
- Reuse session IDs within a workflow and generate new ones for new workflows; watch pagination.
Example Use Cases
- Discover tools for 'Supportbee operations' and select a tool slug from the results.
- Connect to Supportbee with RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE.
- Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with the required arguments.
- Perform a bulk operation using RUBE_REMOTE_WORKBENCH with run_composio_tool().
- Fetch and review the full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs.
