home / skills / composiohq / awesome-claude-skills / flutterwave-automation

flutterwave-automation skill

safe

/flutterwave-automation

This skill automates Flutterwave tasks via Composio's Rube MCP, prioritizing tool discovery and schema accuracy for reliable workflow execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill flutterwave-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: flutterwave-automation
description: "Automate Flutterwave tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Flutterwave Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/flutterwave](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `flutterwave`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Flutterwave tasks through Composio’s Flutterwave toolkit using Rube MCP. It provides a reliable pattern to discover tools, verify connections, and execute Flutterwave operations programmatically. The workflow emphasizes always searching tools first to respect changing schemas and ensure correct inputs.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Flutterwave tool slugs and input schemas, then verifies an active Flutterwave connection via RUBE_MANAGE_CONNECTIONS. Once the connection is ACTIVE, it runs one or more tools with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory parameter) or orchestrates bulk tasks via RUBE_REMOTE_WORKBENCH. Sessions are reused within a workflow and new sessions are generated for separate workflows.

When to use it

Automating payments, refunds, customer lookups, or reconciliation tasks in Flutterwave.
Integrating Flutterwave operations into larger Claude/Composio workflows or pipelines.
Running bulk or scheduled Flutterwave tasks that require consistent schema use.
When you need programmatic discovery of changing tool schemas before execution.
During development or testing to validate tool schemas and execution plans.

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs, input schemas, and execution notes.
Verify Flutterwave connection status with RUBE_MANAGE_CONNECTIONS and complete any returned auth flow until ACTIVE.
Use exact field names and types from the discovered schemas; do not hardcode arguments.
Include an explicit memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs for a single workflow and handle pagination tokens when fetching lists.

Example use cases

Discover available payment and refund endpoints, then execute a refund workflow for a list of transactions.
Automate recurring reconciliation by fetching paginated transaction lists and updating internal records.
Set up a remote workbench script to perform bulk customer data exports via run_composio_tool().
Validate and test new Flutterwave toolkit features by retrieving full schemas with RUBE_GET_TOOL_SCHEMAS.

FAQ

What must I do before running any tool calls?

Always run RUBE_SEARCH_TOOLS to get current schemas and RUBE_MANAGE_CONNECTIONS to ensure the Flutterwave connection is ACTIVE.

Can I hardcode tool slugs and arguments?

No. Tool schemas and slugs can change; hardcoding risks failures. Always use responses from RUBE_SEARCH_TOOLS.