Do I need API keys to use this skill?

No. Setup is via Rube MCP endpoint (https://rube.app/mcp); no API keys are needed.

How do I verify the Flutterwave connection is ready?

Use RUBE_MANAGE_CONNECTIONS with the flutterwave toolkit and check for ACTIVE status before running workflows.

Why must I always search for tools first?

Tool schemas can change; importing the latest tool slugs and arguments ensures compatibility and prevents failures.

flutterwave-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Flutterwave Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/flutterwave

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["flutterwave"]
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 Flutterwave-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `flutterwave`
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/flutterwave-automation/SKILL.md

View on GitHub

Overview

Automate Flutterwave operations using Composio's Flutterwave toolkit through Rube MCP. Always search for current tool schemas before execution to adapt to changes, and ensure an ACTIVE Flutterwave connection before running workflows.

How This Skill Works

The skill discovers available Flutterwave tools by calling RUBE_SEARCH_TOOLS, then validates or establishes the Flutterwave connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the required arguments and memory payload.

When to Use It

Starting a new Flutterwave automation: first discover available tools with RUBE_SEARCH_TOOLS to select the correct tool slug and schema.
Setting up or re-authenticating a Flutterwave connection: run RUBE_MANAGE_CONNECTIONS for the flutterwave toolkit and verify ACTIVE status before execution.
Executing a discovered tool: pass exact field names and types from the tool's input schema and include a memory object in RUBE_MULTI_EXECUTE_TOOL.
Coordinating multi-tool, multi-step workflows: follow the core workflow pattern (discover, check, then execute) across tools, reusing session IDs when appropriate.
Handling tool schema changes or pagination: re-search tool schemas when results are paginated or slugs/arguments change.

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and discover tools with queries: [{use_case: "Flutterwave operations", known_fields: ""}].
Step 2: Manage connection: RUBE_MANAGE_CONNECTIONS with toolkits: ["flutterwave"], session_id: "your_session_id"; ensure ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and the correct tool_slug from discovery, session_id: "your_session_id".

Best Practices

Always call RUBE_SEARCH_TOOLS before running any workflow.
Verify ACTIVE status via RUBE_MANAGE_CONNECTIONS before execution.
Use exact field names and types from the search results.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and handle pagination tokens to complete discovery.

Example Use Cases

Discover Flutterwave tools for a payout automation and run the chosen tool with the correct arguments.
Set up the Flutterwave connection and perform a simple transaction through an automated workflow.
Run a multi-step workflow that discovers tools, checks the connection, and executes a configured tool in one session.
Update an automation when tool schemas change by re-searching tools before execution.
Handle large tool catalogs by paginating through RUBE_SEARCH_TOOLS results until all tools are retrieved.

Frequently Asked Questions

Add this skill to your agents