front-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/front-automation --openclawFront Automation via Rube MCP
Automate Front operations through Composio's Front toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/front
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Front connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfront - 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 toolkitfront - 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: "Front 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 Front task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["front"]
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 Front-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit front |
| 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/front-automation/SKILL.mdView on GitHub Overview
Automate Front operations through Composio's Front toolkit via Rube MCP. Always search tools first for current schemas to ensure you use up-to-date slugs and input fields.
How This Skill Works
Prerequisites include a connected Rube MCP (RUBE_SEARCH_TOOLS available) and an active Front connection via RUBE_MANAGE_CONNECTIONS with toolkit 'front'. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas, including slugs and required arguments. Core workflow: discover tools with RUBE_SEARCH_TOOLS, check the connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with memory: {} and the discovered session_id.
When to Use It
- You need to automate a routine Front operation (e.g., sending a campaign, tagging messages, or routing tickets) using the latest tool schemas.
- You want to integrate Front actions with external triggers via Rube MCP.
- You need to replace hard-coded tool slugs with dynamically discovered ones.
- You’re orchestrating multiple Front tools in a single session workflow.
- You must handle large result sets, including pagination, when discovering tools.
Quick Start
- Step 1: Add the MCP endpoint (https://rube.app/mcp) and connect Front via RUBE_MANAGE_CONNECTIONS.
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current Front tool schemas.
- Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the session_id and memory.
Best Practices
- Always run RUBE_SEARCH_TOOLS before executing any workflow.
- Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
- Use exact field names and types from the tool schemas returned by search.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and fetch new ones for new tasks; monitor pagination.
Example Use Cases
- Discover a Front tool slug for sending a campaign and execute it with the required args.
- Tag or route messages based on sender domain using a Front tool discovered at runtime.
- Chain discovery, connection check, and execution to automate a multi-step Front workflow in a single session.
- Iterate over multiple pages of tool schemas by handling pagination tokens to cover all Front use cases.
- Reuse a single session_id to perform several Front tasks in sequence.
