# How to connect Folk to OpenClaw (paste one key, 23 tools) > Connect Folk to OpenClaw with ClawLink: paste your Folk key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/folk The usual route to Folk 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 Folk setup: install one ClawHub skill, connect Folk in the browser, and OpenClaw can call real Folk 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 Folk. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Folk** — 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 folk # connect Folk (browser OAuth) npx -y @useclawlink/cli actions folk # list available actions npx -y @useclawlink/cli run folk --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 Folk in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Folk API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Folk, 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 Folk is connected in the dashboard, that agent calls the same 23 Folk 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). ## Folk MCP for OpenClaw Looking for a Folk MCP server for OpenClaw? ClawLink connects Folk to OpenClaw and exposes 23 Folk 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 Folk integration](https://claw-link.dev/hermes/folk) works the same way. ## What the OpenClaw Folk integration can do 23 Folk tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 23. ### 19 of 23 Folk tools for OpenClaw | Tool | What it does | |---|---| | **Get company** `folk_get_company` | Retrieve an existing company by its ID | | **Get current workspace user** `folk_get_current_workspace_user` | Get details of the current authenticated workspace user | | **Get note** `folk_get_note` | Retrieve an existing note by its ID | | **Get person** `folk_get_person` | Retrieve an existing person by their ID | | **Get user** `folk_get_user` | Retrieve a user by their unique identifier | | **List companies** `folk_list_companies` | List companies in the workspace | | **List group custom fields** `folk_list_group_custom_fields` | List custom fields for a specific group and entity type | | **List groups** `folk_list_groups` | List workspace groups | | **List notes** `folk_list_notes` | List notes in the workspace | | **List people** `folk_list_people` | List people in the workspace | | **List reminders** `folk_list_reminders` | List reminders in the workspace | | **List users** `folk_list_users` | List workspace users | | **List webhooks** `folk_list_webhooks` | List webhooks in the workspace | | **Create company** `folk_create_company` | Creates a new company in the Folk workspace with the specified details | | **Create note** `folk_create_note` | Create a new note in the Folk workspace | | **Create person** `folk_create_person` | Creates a new person in the Folk workspace with the specified details | | **Update company** `folk_update_company` | Update an existing company in the workspace | | **Update note** `folk_update_note` | Update an existing note in the workspace | | **Update person** `folk_update_person` | Update an existing person in the workspace | ## Example prompts **Get Company** > Pull the relevant data from Folk, summarize it in plain English, and point out anything that needs attention. **Get Current Workspace User** > Pull the relevant data from Folk, summarize it in plain English, and point out anything that needs attention. **Get Note** > Pull the relevant data from Folk, summarize it in plain English, and point out anything that needs attention. **Get Person** > Pull the relevant data from Folk, 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 Folk working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Folk API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Folk 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 Folk. | 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 Folk actions to the runtime in a format your agent can reliably use. | 23 tools for Folk are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Folk 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 Folk in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Folk 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 Folk skill but can't call the tools The ClawHub skill teaches OpenClaw about Folk, but the calls run through the ClawLink plugin and your connected account. Make sure Folk 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 Folk 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 Folk tools Folk 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 Folk 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. ### Folk 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 Folk has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Folk integration? Yes. ClawLink is the fastest way to connect OpenClaw to Folk: link your Folk account once in the browser and OpenClaw can call the Folk API through 23 ready-made tools — no custom code or token handling. ### How do I add Folk to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Folk skill from ClawHub, then you click Connect in the dashboard to authorize Folk. OpenClaw calls the tools from the next message — no config files, and the Folk key you paste is stored server-side instead of in your environment. ### How long does it take to connect Folk to OpenClaw? About two minutes. Sign in, click Connect next to Folk in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Folk 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 Folk working from chat. ### OpenClaw installed the Folk skill but can't call the tools The ClawHub skill teaches OpenClaw about Folk, but the calls run through the ClawLink plugin and your connected account. Make sure Folk 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 tools](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows