Procfu Automation
It enables users to streamline workflows within Procfu by leveraging automated tools.
Install
npx promptshop add procfu-automationDetails
What This Skill Does
This skill automates Procfu operations using Composio's Procfu toolkit via Rube MCP. It enables users to streamline workflows within Procfu by leveraging automated tools. It is designed for users seeking to integrate Procfu with other systems and automate repetitive tasks.
When to Use
Automate data extraction from ProcfuTrigger Procfu workflows from external eventsUpdate Procfu records automaticallyCreate new records in ProcfuManage Procfu users and permissionsSync Procfu data with other platforms
Key Features
Uses Rube MCP for tool discovery and executionRequires an active Procfu connectionProvides a structured workflow pattern for automationEmphasizes the importance of dynamic schema discoveryOffers connection management via RUBE_MANAGE_CONNECTIONSUses RUBE_MULTI_EXECUTE_TOOL for task execution
Manual Installation
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 |
Automate Procfu operations through Composio's Procfu toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/procfu