How to connect Userflow to OpenClaw
Connect Userflow to OpenClaw with ClawLink: paste your Userflow key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
UserflowAPI KEYMCPUser onboarding software.. Once connected, OpenClaw can read and act on Userflow from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Userflow 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 Userflow setup: install one ClawHub skill, connect Userflow in the browser, and OpenClaw can call real Userflow 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 Userflow.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Userflow
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Userflow?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Userflow in the ClawLink dashboard — paste your Userflow API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Userflow, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Userflow is connected in the dashboard, that agent calls the same 18 Userflow tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Userflow MCP for OpenClaw
Looking for a Userflow MCP server for OpenClaw? ClawLink connects Userflow to OpenClaw and exposes 18 Userflow tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Userflow integration works the same way.
What the OpenClaw Userflow integration can do
18 Userflow tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 18.
15 of 18 Userflow tools for OpenClaw
| Tool | What it does |
|---|---|
Get a content object userflow_get_a_content_object | Retrieve details of a specific content object (flow, checklist, or launcher) by ID |
Get a content version userflow_get_a_content_version | Retrieve details of a specific content version by ID |
Get a group userflow_get_a_group | Retrieve details of a specific group (company) by group_id |
Get a user userflow_get_a_user | Retrieve details of a specific user by user_id |
List attribute definitions userflow_list_attribute_definitions | Retrieve all attribute definitions for users and groups tracked by Userflow |
List content userflow_list_content | Retrieve all content (flows, checklists, and launchers) in your Userflow account |
List content sessions userflow_list_content_sessions | Retrieve all content sessions tracking user interactions with content |
List content versions userflow_list_content_versions | Retrieve all versions of content including survey questions and checklist tasks |
List event definitions userflow_list_event_definitions | Retrieve all event definitions tracked in Userflow |
List groups userflow_list_groups | Retrieve all groups (companies) in your Userflow account with pagination and filtering support |
List users userflow_list_users | Retrieve a paginated list of all users |
Create or update a group userflow_create_or_update_a_group | Create a new group or update an existing group (also referred to as companies in the Userflow |
Create or update a user userflow_create_or_update_a_user | Create a new user or update an existing user in Userflow |
Track an event userflow_track_an_event | Record a custom event for a user or group for analytics and personalization |
Remove a user from a group userflow_remove_a_user_from_a_group | Remove a user from a group (group membership) |
Try it: find the Userflow tool you need
Browse the 15 Userflow tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Userflow, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Userflow, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Userflow, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Userflow, 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 Userflow working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Userflow API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Userflow 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 Userflow. | 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 Userflow actions to the runtime in a format your agent can reliably use. | 18 tools for Userflow are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Userflow 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 Userflow in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Userflow key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Userflow skill but can't call the tools
The ClawHub skill teaches OpenClaw about Userflow, but the calls run through the ClawLink plugin and your connected account. Make sure Userflow 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 Userflow 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 Userflow tools
Userflow 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 Userflow 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.
Userflow 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 Userflow has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Userflow integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Userflow: link your Userflow account once in the browser and OpenClaw can call the Userflow API through 18 ready-made tools — no custom code or token handling.
How do I add Userflow to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Userflow skill from ClawHub, then you click Connect in the dashboard to authorize Userflow. OpenClaw calls the tools from the next message — no config files, and the Userflow key you paste is stored server-side instead of in your environment.
How long does it take to connect Userflow to OpenClaw?
About two minutes. Sign in, click Connect next to Userflow in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Userflow 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 Userflow working from chat.
OpenClaw installed the Userflow skill but can't call the tools
The ClawHub skill teaches OpenClaw about Userflow, but the calls run through the ClawLink plugin and your connected account. Make sure Userflow 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.
