How to connect EnforcedFlow to OpenClaw
Connect EnforcedFlow to OpenClaw with ClawLink: paste your EnforcedFlow key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
EnforcedFlowAPI KEYMCPEnforcedFlow routes work across teams with configurable advanced round-robin groups, agent criteria, availability, and email assignments.. Once connected, OpenClaw can read and act on EnforcedFlow from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to EnforcedFlow 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 EnforcedFlow setup: install one ClawHub skill, connect EnforcedFlow in the browser, and OpenClaw can call real EnforcedFlow 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 EnforcedFlow.
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 EnforcedFlow
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with EnforcedFlow?"
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 EnforcedFlow in the ClawLink dashboard — paste your EnforcedFlow API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from EnforcedFlow, 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 EnforcedFlow is connected in the dashboard, that agent calls the same 5 EnforcedFlow tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
EnforcedFlow MCP for OpenClaw
Looking for a EnforcedFlow MCP server for OpenClaw? ClawLink connects EnforcedFlow to OpenClaw and exposes 5 EnforcedFlow tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes EnforcedFlow integration works the same way.
What the OpenClaw EnforcedFlow integration can do
5 EnforcedFlow tools are ready for OpenClaw once the account is connected.
All 5 EnforcedFlow tools for OpenClaw
| Tool | What it does |
|---|---|
Get group fields enforcedflow_get_group_fields | Get detailed routing-field configuration and metadata field names for one round-robin group |
List group agents enforcedflow_list_group_agents | List agents in a round-robin group, optionally filtering by active status, with metadata and |
List groups enforcedflow_list_groups | List round-robin groups accessible to the connected account, including group IDs and summary |
Upsert group agent enforcedflow_upsert_group_agent | Update the first agent matching a filter, or create an agent when the filter matches none |
Select next agent enforcedflow_select_next_agent | Select the next available agent for a round-robin group using optional configured criteria |
Try it: find the EnforcedFlow tool you need
Browse the 5 EnforcedFlow 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 EnforcedFlow, summarize it in plain English, and point out anything that needs attention.
List the relevant items in EnforcedFlow, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in EnforcedFlow, group them by priority, and recommend what OpenClaw should do next.
Use EnforcedFlow to upsert group agent and walk me through the result in plain English.
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 EnforcedFlow working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the EnforcedFlow API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected EnforcedFlow 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 EnforcedFlow. | 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 EnforcedFlow actions to the runtime in a format your agent can reliably use. | 5 tools for EnforcedFlow are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes EnforcedFlow 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 EnforcedFlow in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the EnforcedFlow 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 EnforcedFlow skill but can't call the tools
The ClawHub skill teaches OpenClaw about EnforcedFlow, but the calls run through the ClawLink plugin and your connected account. Make sure EnforcedFlow 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 EnforcedFlow 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 EnforcedFlow tools
EnforcedFlow 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 EnforcedFlow 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.
EnforcedFlow 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 EnforcedFlow 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 EnforcedFlow integration?
Yes. ClawLink is the fastest way to connect OpenClaw to EnforcedFlow: link your EnforcedFlow account once in the browser and OpenClaw can call the EnforcedFlow API through 5 ready-made tools — no custom code or token handling.
How do I add EnforcedFlow to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink EnforcedFlow skill from ClawHub, then you click Connect in the dashboard to authorize EnforcedFlow. OpenClaw calls the tools from the next message — no config files, and the EnforcedFlow key you paste is stored server-side instead of in your environment.
How long does it take to connect EnforcedFlow to OpenClaw?
About two minutes. Sign in, click Connect next to EnforcedFlow in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring EnforcedFlow 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 EnforcedFlow working from chat.
OpenClaw installed the EnforcedFlow skill but can't call the tools
The ClawHub skill teaches OpenClaw about EnforcedFlow, but the calls run through the ClawLink plugin and your connected account. Make sure EnforcedFlow 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.
