What is procfu-automation?

A workflow pattern to automate Procfu operations via the Rube MCP toolkit in Composio, with emphasis on discovering current tool schemas before execution.

What are the prerequisites?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Procfu connection via RUBE_MANAGE_CONNECTIONS with toolkit 'procfu'.

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS prior to execution to fetch up-to-date tool slugs and input schemas, then use exact fields from those results.

procfu-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/procfu-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Procfu Automation via Rube MCP

Automate Procfu operations through Composio's Procfu toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/procfu

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Procfu connection via RUBE_MANAGE_CONNECTIONS with toolkit procfu
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 procfu
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: "Procfu 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 Procfu task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["procfu"]
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 Procfu-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `procfu`
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/procfu-automation/SKILL.mdView on GitHub

Overview

Procfu Automation via Rube MCP enables automating Procfu operations using Composio's toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to ensure compatibility. Requires an active Rube MCP connection and a configured Procfu toolkit.

How This Skill Works

Start by discovering available Procfu tools with RUBE_SEARCH_TOOLS to fetch up-to-date input schemas. Then confirm the Procfu connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, including a memory payload and an active session_id. Iterate through discovered tools and validate schemas and fields match the retrieved definitions.

When to Use It

Setting up a new Procfu automation via Rube MCP and ensuring the Procfu toolkit is connected
Running Procfu tasks after calling RUBE_SEARCH_TOOLS to fetch current tool schemas
Updating workflows when tool schemas change to avoid hard-coding slugs or fields
Reusing session IDs across steps for a single automation workflow
Performing bulk Procfu operations through RUBE_REMOTE_WORKBENCH when needed

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys required)
Step 2: Verify RUBE_SEARCH_TOOLS responds and then call RUBE_MANAGE_CONNECTIONS with toolkit 'procfu' to ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and memory, session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any Procfu tool to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before tool execution
Use exact field names and types from the tool schemas returned by search
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination if present

Example Use Cases

Discover Procfu tools with RUBE_SEARCH_TOOLS, then run a data export tool via RUBE_MULTI_EXECUTE_TOOL with the proper arguments
Set up a new Procfu automation flow, verify connection, and execute a cleanup task using discovered tool slugs
Automate a Procfu report generation by fetching current schemas, then executing the report tool with session_id continuity
Perform bulk Procfu operations through RUBE_REMOTE_WORKBENCH by orchestrating multiple tool executions in one workflow
Handle a Procfu schema update by re-running RUBE_SEARCH_TOOLS to refresh slugs and field names before execution

Frequently Asked Questions

Add this skill to your agents