What is expofp-automation?

It automates Expofp tasks via Rube MCP (Composio) using the Expofp toolkit.

What must I do before running workflows?

Always call RUBE_SEARCH_TOOLS to get current tool schemas and confirm an ACTIVE Expofp connection.

How do I execute an Expofp tool correctly?

Discover the tool with RUBE_SEARCH_TOOLS, then run RUBE_MULTI_EXECUTE_TOOL using the exact schema fields, include memory, and reuse the session_id for the workflow.

expofp-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Expofp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/expofp

Prerequisites

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

Step 2: Check Connection

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

Overview

Expofp-automation enables automating Expofp operations through Composio's Expofp toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution to ensure compatibility and avoid stale configurations.

How This Skill Works

Connect Rube MCP and ensure RUBE_SEARCH_TOOLS is available. Discover tools and their input schemas, then verify an ACTIVE Expofp connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tools with RUBE_MULTI_EXECUTE_TOOL, including a memory object and an existing session_id.

When to Use It

You need to automate recurring Expofp operations with up-to-date tool schemas.
You want to orchestrate multiple Expofp tools in a single, end-to-end workflow.
You must confirm the Rube MCP connection is ACTIVE before running tools.
You need to discover available Expofp tools and their input schemas prior to execution.
You require session reuse within a workflow and must include a memory parameter in tool calls.

Quick Start

Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS returns Expofp tools.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'expofp' and confirm ACTIVE status.
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug, proper arguments from the schema, a memory object, and your session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs or args.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new sessions only for separate runs.

Example Use Cases

Automate a monthly Expofp report by discovering tools, ensuring an ACTIVE connection, then executing the required tool with a populated input schema.
Batch run several Expofp tools in one workflow to process a data pipeline, using the discovered tool slugs and a shared session.
Daily validation of the Expofp connection before running automated tasks to prevent failures due to disconnected state.
Handle large tool sets by using RUBE_SEARCH_TOOLS with pagination tokens, then execute the chosen tool(s) with exact schemas.
Create a new Expofp automation workflow that reuses a session across steps and includes a memory payload for stateful operations.

Frequently Asked Questions

Add this skill to your agents