# How to connect Flowiseai to OpenClaw (paste one key, 29 tools) > Connect Flowiseai to OpenClaw with ClawLink: paste your Flowiseai key once and 29 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/flowiseai The usual route to Flowiseai 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 Flowiseai setup: install one ClawHub skill, connect Flowiseai in the browser, and OpenClaw can call real Flowiseai 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 Flowiseai. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Flowiseai** — 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 flowiseai # connect Flowiseai (browser OAuth) npx -y @useclawlink/cli actions flowiseai # list available actions npx -y @useclawlink/cli run flowiseai --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 Flowiseai in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Flowiseai API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Flowiseai, 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 Flowiseai is connected in the dashboard, that agent calls the same 29 Flowiseai 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). ## Flowiseai MCP for OpenClaw Looking for a Flowiseai MCP server for OpenClaw? ClawLink connects Flowiseai to OpenClaw and exposes 29 Flowiseai 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 Flowiseai integration](https://claw-link.dev/hermes/flowiseai) works the same way. ## What the OpenClaw Flowiseai integration can do 29 Flowiseai tools are ready for OpenClaw once the account is connected. The 24 below are the ones people reach for most; your agent can call all 29. ### 24 of 29 Flowiseai tools for OpenClaw | Tool | What it does | |---|---| | **Get all chat message feedback** `flowiseai_get_all_chat_message_feedback` | List all chat message feedbacks for a chatflow | | **Get all chatflows** `flowiseai_get_all_chatflows` | Retrieves all chatflows from the authenticated FlowiseAI account | | **Get all leads for chatflow** `flowiseai_get_all_leads_for_chatflow` | Retrieve all leads for a specific chatflow | | **Get all upsert history** `flowiseai_get_all_upsert_history` | Retrieve all upsert history records for a specific chatflow | | **Get all variables** `flowiseai_get_all_variables` | Retrieve a list of all variables | | **Get document store by ID** `flowiseai_get_document_store_by_id` | Retrieve a document store by its ID | | **Get document store file chunks** `flowiseai_get_document_store_file_chunks` | Get chunks from a specific document loader | | **Get single chatflow** `flowiseai_get_single_chatflow` | Retrieve a chatflow by its ID | | **Get tool by ID** `flowiseai_get_tool_by_id` | Retrieve a specific FlowiseAI tool by its ID | | **List all tools** `flowiseai_list_all_tools` | Retrieve a list of all tools | | **List assistants** `flowiseai_list_assistants` | Retrieve a list of all assistants | | **List chat messages** `flowiseai_list_chat_messages` | List chat messages of a chatflow | | **Ping server** `flowiseai_ping_server` | Ping the FlowiseAI server to verify it is running and accessible | | **Create chatflow** `flowiseai_create_chatflow` | Creates a new chatflow in FlowiseAI | | **Create document store** `flowiseai_create_document_store` | Creates a new document store in FlowiseAI | | **Create lead** `flowiseai_create_lead` | Create a new lead in a chatflow | | **Create tool** `flowiseai_create_tool` | Create a new FlowiseAI tool | | **Create variable** `flowiseai_create_variable` | Creates a new variable in FlowiseAI | | **Edit document store file chunk** `flowiseai_edit_document_store_file_chunk` | Update a specific chunk in a FlowiseAI document store | | **Update chatflow details** `flowiseai_update_chatflow_details` | Update details of an existing chatflow | | **Update document store** `flowiseai_update_document_store` | Update a specific document store | | **Update tool by ID** `flowiseai_update_tool_by_id` | Updates a FlowiseAI tool's properties by its ID | | **Update variable** `flowiseai_update_variable` | Update a variable by its ID | | **Clone chatflow** `flowiseai_clone_chatflow` | Clone an existing chatflow | ## Example prompts **Get All Chat Message Feedback** > Pull the relevant data from Flowiseai, summarize it in plain English, and point out anything that needs attention. **Get All Chatflows** > Pull the relevant data from Flowiseai, summarize it in plain English, and point out anything that needs attention. **Get All Leads For Chatflow** > Pull the relevant data from Flowiseai, summarize it in plain English, and point out anything that needs attention. **Get All Upsert History** > Pull the relevant data from Flowiseai, 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 Flowiseai working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Flowiseai API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Flowiseai 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 Flowiseai. | 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 Flowiseai actions to the runtime in a format your agent can reliably use. | 29 tools for Flowiseai are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Flowiseai 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 Flowiseai in the browser, and the 29 tools above work from chat. There is no SDK and no config file, and the Flowiseai 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 Flowiseai skill but can't call the tools The ClawHub skill teaches OpenClaw about Flowiseai, but the calls run through the ClawLink plugin and your connected account. Make sure Flowiseai 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 Flowiseai 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 Flowiseai tools Flowiseai 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 Flowiseai 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. ### Flowiseai 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 Flowiseai has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Flowiseai integration? Yes. ClawLink is the fastest way to connect OpenClaw to Flowiseai: link your Flowiseai account once in the browser and OpenClaw can call the Flowiseai API through 29 ready-made tools — no custom code or token handling. ### How do I add Flowiseai to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Flowiseai skill from ClawHub, then you click Connect in the dashboard to authorize Flowiseai. OpenClaw calls the tools from the next message — no config files, and the Flowiseai key you paste is stored server-side instead of in your environment. ### How long does it take to connect Flowiseai to OpenClaw? About two minutes. Sign in, click Connect next to Flowiseai in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Flowiseai 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 Flowiseai working from chat. ### OpenClaw installed the Flowiseai skill but can't call the tools The ClawHub skill teaches OpenClaw about Flowiseai, but the calls run through the ClawLink plugin and your connected account. Make sure Flowiseai 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 - [Connect DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.