# How to connect Forcemanager to OpenClaw (paste one key, 20 tools) > Connect Forcemanager to OpenClaw with ClawLink: paste your Forcemanager key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/forcemanager The usual route to Forcemanager 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 Forcemanager setup: install one ClawHub skill, connect Forcemanager in the browser, and OpenClaw can call real Forcemanager 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 Forcemanager. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Forcemanager** — 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 forcemanager # connect Forcemanager (browser OAuth) npx -y @useclawlink/cli actions forcemanager # list available actions npx -y @useclawlink/cli run forcemanager --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 Forcemanager in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Forcemanager API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Forcemanager, 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 Forcemanager is connected in the dashboard, that agent calls the same 20 Forcemanager 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). ## Forcemanager MCP for OpenClaw Looking for a Forcemanager MCP server for OpenClaw? ClawLink connects Forcemanager to OpenClaw and exposes 20 Forcemanager 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 Forcemanager integration](https://claw-link.dev/hermes/forcemanager) works the same way. ## What the OpenClaw Forcemanager integration can do 20 Forcemanager tools are ready for OpenClaw once the account is connected. The 13 below are the ones people reach for most; your agent can call all 20. ### 13 of 20 Forcemanager tools for OpenClaw | Tool | What it does | |---|---| | **Get activity** `forcemanager_get_activity` | Retrieves a single activity by its ID from ForceManager CRM | | **Get company** `forcemanager_get_company` | Retrieve a single company by its ID from ForceManager | | **Get internal ID** `forcemanager_get_internal_id` | Retrieve ForceManager internal IDs mapping for a given externalId and entity type | | **Get product** `forcemanager_get_product` | Retrieve a single product by its ID from ForceManager/Sage Sales Management | | **Get sales order line** `forcemanager_get_sales_order_line` | Retrieves a single sales order line by ID from ForceManager | | **Get user** `forcemanager_get_user` | Retrieves a single ForceManager user by their ID, returning comprehensive user information | | **Get view** `forcemanager_get_view` | Get a single view by ID | | **List views** `forcemanager_list_views` | List saved view filters | | **Update activity** `forcemanager_update_activity` | Update an existing activity by ID | | **Update company** `forcemanager_update_company` | Update Company | | **Update product** `forcemanager_update_product` | Updates an existing product by ID in ForceManager | | **Update sales order** `forcemanager_update_sales_order` | Update Sales Order | | **Update sales order line** `forcemanager_update_sales_order_line` | Update sales order line by ID | ## Example prompts **Get Activity** > Pull the relevant data from Forcemanager, summarize it in plain English, and point out anything that needs attention. **Get Company** > Pull the relevant data from Forcemanager, summarize it in plain English, and point out anything that needs attention. **Get Internal Id** > Pull the relevant data from Forcemanager, summarize it in plain English, and point out anything that needs attention. **Get Product** > Pull the relevant data from Forcemanager, 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 Forcemanager working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Forcemanager API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Forcemanager 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 Forcemanager. | 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 Forcemanager actions to the runtime in a format your agent can reliably use. | 20 tools for Forcemanager are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Forcemanager 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 Forcemanager in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Forcemanager 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 Forcemanager skill but can't call the tools The ClawHub skill teaches OpenClaw about Forcemanager, but the calls run through the ClawLink plugin and your connected account. Make sure Forcemanager 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 Forcemanager 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 Forcemanager tools Forcemanager 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 Forcemanager 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. ### Forcemanager 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 Forcemanager has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Forcemanager integration? Yes. ClawLink is the fastest way to connect OpenClaw to Forcemanager: link your Forcemanager account once in the browser and OpenClaw can call the Forcemanager API through 20 ready-made tools — no custom code or token handling. ### How do I add Forcemanager to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Forcemanager skill from ClawHub, then you click Connect in the dashboard to authorize Forcemanager. OpenClaw calls the tools from the next message — no config files, and the Forcemanager key you paste is stored server-side instead of in your environment. ### How long does it take to connect Forcemanager to OpenClaw? About two minutes. Sign in, click Connect next to Forcemanager in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Forcemanager 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 Forcemanager working from chat. ### OpenClaw installed the Forcemanager skill but can't call the tools The ClawHub skill teaches OpenClaw about Forcemanager, but the calls run through the ClawLink plugin and your connected account. Make sure Forcemanager 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 - [HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Connect Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows