# How to connect Flutterwave to OpenClaw (paste one key, 53 tools) > Connect Flutterwave to OpenClaw with ClawLink: paste your Flutterwave key once and 53 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/flutterwave The usual route to Flutterwave access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Flutterwave setup: install one ClawHub skill, connect Flutterwave in the browser, and OpenClaw can call real Flutterwave actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Flutterwave. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Flutterwave** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect flutterwave # connect Flutterwave (browser OAuth) npx -y @useclawlink/cli actions flutterwave # list available actions npx -y @useclawlink/cli run flutterwave --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Flutterwave in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Flutterwave API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Flutterwave, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Flutterwave is connected in the dashboard, that agent calls the same 53 Flutterwave tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Flutterwave MCP for OpenClaw Looking for a Flutterwave MCP server for OpenClaw? ClawLink connects Flutterwave to OpenClaw and exposes 53 Flutterwave tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Flutterwave integration](https://claw-link.dev/hermes/flutterwave) works the same way. ## What the OpenClaw Flutterwave integration can do 53 Flutterwave tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 53. ### 30 of 53 Flutterwave tools for OpenClaw | Tool | What it does | |---|---| | **Fetch beneficiary** `flutterwave_fetch_beneficiary` | Retrieve details of a specific beneficiary by ID | | **Fetch subaccount** `flutterwave_fetch_subaccount` | Retrieve details of a specific subaccount by ID | | **Generate transaction reference** `flutterwave_generate_transaction_reference` | Generate a unique transaction reference | | **Get all subscriptions** `flutterwave_get_all_subscriptions` | Retrieve all subscriptions, including cancelled ones | | **Get all transactions** `flutterwave_get_all_transactions` | Retrieve a list of all transactions with optional filters | | **Get all wallet balances** `flutterwave_get_all_wallet_balances` | Retrieve all wallet balances across currencies | | **Get balances per currency** `flutterwave_get_balances_per_currency` | Retrieve wallet balance for a specific currency | | **Get bank branches** `flutterwave_get_bank_branches` | Retrieve branch codes for a specific bank | | **Get banks by country** `flutterwave_get_banks_by_country` | Retrieve all banks in a specified country | | **Get bill categories** `flutterwave_get_bill_categories` | Retrieve available bill categories | | **Get bulk tokenized charge** `flutterwave_get_bulk_tokenized_charge` | Retrieve the status of a bulk tokenized charge operation by ID | | **Get bulk virtual account** `flutterwave_get_bulk_virtual_account` | Fetch bulk virtual account details using batch ID | | **Get multiple refund transactions** `flutterwave_get_multiple_refund_transactions` | Retrieve multiple refund transactions with optional filters | | **Get payment plan** `flutterwave_get_payment_plan` | Retrieve details of a specific payment plan by ID | | **Get payment plans** `flutterwave_get_payment_plans` | Retrieve a list of all payment plans | | **Get refund** `flutterwave_get_refund` | Retrieve details of a specific refund by ID | | **Get transaction** `flutterwave_get_transaction` | Retrieve details of a specific transaction by ID | | **Get transaction fee** `flutterwave_get_transaction_fee` | Retrieve the fee for a specific transaction | | **Get transfer fee** `flutterwave_get_transfer_fee` | Retrieve the fee for initiating a transfer | | **Get transfer rates** `flutterwave_get_transfer_rates` | Retrieve exchange rates for transfers between currencies | | **Get virtual account number** `flutterwave_get_virtual_account_number` | Fetch details of a virtual account number by order reference | | **Get wallet statement** `flutterwave_get_wallet_statement` | Retrieve wallet balance history with optional filters | | **List all beneficiaries** `flutterwave_list_all_beneficiaries` | List all saved beneficiaries | | **List biller products** `flutterwave_list_biller_products` | Retrieve all products available under a specific biller | | **List billers** `flutterwave_list_billers` | Retrieve available billers | | **List chargebacks** `flutterwave_list_chargebacks` | Retrieve a list of chargebacks with optional filtering by Flutterwave reference | | **List payout subaccount refunds** `flutterwave_list_payout_subaccount_refunds` | List all payout subaccount refunds with pagination support | | **List payout subaccounts** `flutterwave_list_payout_subaccounts` | List all payout subaccounts | | **List recurring bills** `flutterwave_list_recurring_bills` | Retrieve all recurring bill payments | | **List settlements** `flutterwave_list_settlements` | Retrieve all settlements with optional filters | ## Example prompts **Fetch Beneficiary** > Pull the relevant data from Flutterwave, summarize it in plain English, and point out anything that needs attention. **Fetch Subaccount** > Pull the relevant data from Flutterwave, summarize it in plain English, and point out anything that needs attention. **Generate Transaction Reference** > Use Flutterwave to generate transaction reference and walk me through the result in plain English. **Get All Subscriptions** > Pull the relevant data from Flutterwave, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Flutterwave working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Flutterwave API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Flutterwave account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Flutterwave. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Flutterwave actions to the runtime in a format your agent can reliably use. | 53 tools for Flutterwave are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Flutterwave to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Flutterwave in the browser, and the 53 tools above work from chat. There is no SDK and no config file, and the Flutterwave key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Flutterwave skill but can't call the tools The ClawHub skill teaches OpenClaw about Flutterwave, but the calls run through the ClawLink plugin and your connected account. Make sure Flutterwave is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Flutterwave from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Flutterwave tools Flutterwave tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Flutterwave call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Flutterwave returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Flutterwave has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Flutterwave integration? Yes. ClawLink is the fastest way to connect OpenClaw to Flutterwave: link your Flutterwave account once in the browser and OpenClaw can call the Flutterwave API through 53 ready-made tools — no custom code or token handling. ### How do I add Flutterwave to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Flutterwave skill from ClawHub, then you click Connect in the dashboard to authorize Flutterwave. OpenClaw calls the tools from the next message — no config files, and the Flutterwave key you paste is stored server-side instead of in your environment. ### How long does it take to connect Flutterwave to OpenClaw? About two minutes. Sign in, click Connect next to Flutterwave in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Flutterwave up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Flutterwave working from chat. ### OpenClaw installed the Flutterwave skill but can't call the tools The ClawHub skill teaches OpenClaw about Flutterwave, but the calls run through the ClawLink plugin and your connected account. Make sure Flutterwave is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Stripe](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Connect Zoho Books](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp tools](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts