Flutterwave Automation

What This Skill Does

This skill automates Flutterwave operations using the Composio Flutterwave toolkit via Rube MCP. It's designed for users who want to streamline payment processing and related tasks within their workflows. The skill requires an active Flutterwave connection and Rube MCP setup.

When to Use

• Process a payment through Flutterwave.
• Retrieve transaction details.
• Verify payment status.
• Initiate a refund.
• Manage Flutterwave payouts.
• Automate reconciliation processes.

Key Features

Automates Flutterwave tasks via Rube MCP. Uses RUBE_SEARCH_TOOLS for tool discovery. Requires active Flutterwave connection via RUBE_MANAGE_CONNECTIONS. Executes tools using RUBE_MULTI_EXECUTE_TOOL. Provides access to Flutterwave's payment processing capabilities. Ensures schema compliance for tool arguments.

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 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

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: {}

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

Powered by Composio Flutterwave Automation via Rube MCP