# How to connect Affinda to OpenClaw (paste one key, 105 tools) > Connect Affinda to OpenClaw with ClawLink: paste your Affinda key once and 105 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/affinda The usual route to Affinda 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 Affinda setup: install one ClawHub skill, connect Affinda in the browser, and OpenClaw can call real Affinda actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/affinda ## Setup It takes three steps to connect OpenClaw to Affinda. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Affinda** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 affinda # connect Affinda (browser OAuth) npx -y @useclawlink/cli actions affinda # list available actions npx -y @useclawlink/cli run affinda --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 Affinda in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Affinda API key once. Verify the connection by asking OpenClaw: > Use Affinda to add tag to documents and walk me through the result in plain English. ### 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 Affinda is connected in the dashboard, that agent calls the same 105 Affinda 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). ## Affinda MCP for OpenClaw Looking for a Affinda MCP server for OpenClaw? ClawLink connects Affinda to OpenClaw and exposes 105 Affinda 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 Affinda integration](https://claw-link.dev/hermes/affinda) works the same way. ## What the OpenClaw Affinda integration can do 105 Affinda tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 105. ### 30 of 105 Affinda tools for OpenClaw | Tool | What it does | |---|---| | **Add tag to documents** `affinda_add_tag_to_documents` | Add a tag to multiple documents in a single operation | | **Batch update annotations** `affinda_batch_update_annotations` | Batch update multiple document annotations in a single API call | | **Create API user** `affinda_create_api_user` | Create a new API user within an organization | | **Create batch annotations** `affinda_create_batch_annotations` | Batch create multiple document annotations in a single API call | | **Create job description search** `affinda_create_job_description_search` | Search through parsed job descriptions using custom criteria or resume matching | | **Create resume search** `affinda_create_resume_search` | Search through parsed resumes using three methods: match to a job description, match to a resume, or custom criteria | | **Get all API users** `affinda_get_all_api_users` | Retrieve a list of all API users | | **Get all document splitters** `affinda_get_all_document_splitters` | Get a list of all document splitters | | **Get all invitations** `affinda_get_all_invitations` | Retrieve all invitations you created or sent to you | | **Get all organization memberships** `affinda_get_all_organization_memberships` | Retrieve all organization memberships across the account | | **Get all tags** `affinda_get_all_tags` | List all tags. Use after confirming authentication to fetch tags across workspaces. | | **Get all validation results** `affinda_get_all_validation_results` | List validation results for documents | | **Get all workspace memberships** `affinda_get_all_workspace_memberships` | Retrieve all workspace memberships across the account | | **Get annotations** `affinda_get_annotations` | Retrieves all annotations for a specific document | | **Get collection** `affinda_get_collection` | Retrieve details of a specific collection by its ID | | **Get collections** `affinda_get_collections` | Retrieve a list of all collections | | **Get data source** `affinda_get_data_source` | Retrieve details of a specific mapping data source by its identifier | | **Get data source value** `affinda_get_data_source_value` | Retrieve a specific value from a mapping data source | | **Get data source values** `affinda_get_data_source_values` | Retrieve all values from a mapping data source | | **Get document** `affinda_get_document` | Retrieve full details and parsed data for a specific document by its identifier | | **Get document redacted** `affinda_get_document_redacted` | Retrieve the redacted version of a document as a PDF file | | **Get document splitter** `affinda_get_document_splitter` | Retrieve details of a specific document splitter by its identifier | | **Get document type** `affinda_get_document_type` | Retrieve details of a specific document type by its ID | | **Get document type json schema** `affinda_get_document_type_json_schema` | Generate a JSON schema from a document type by its identifier | | **Get document type pydantic models** `affinda_get_document_type_pydantic_models` | Generate Pydantic model code from a document type's schema | | **Get document types** `affinda_get_document_types` | Retrieve all document types accessible to the authenticated user | | **Get documents** `affinda_get_documents` | Retrieve a list of all documents | | **Get extractor** `affinda_get_extractor` | Retrieve detailed information about a specific extractor by its identifier | | **Get extractors** `affinda_get_extractors` | Retrieve all extractors available for an organization | | **Get index documents** `affinda_get_index_documents` | Retrieve all indexed documents for a specific index | ## Example prompts **Add Tag To Documents** > Use Affinda to add tag to documents and walk me through the result in plain English. **Batch Update Annotations** > Use Affinda to batch update annotations and walk me through the result in plain English. **Create Api User** > Create it in Affinda for me, then confirm the important fields before you finish. **Create Batch Annotations** > Create it in Affinda for me, then confirm the important fields before you finish. ## 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 Affinda working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Affinda API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Affinda 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 Affinda. | 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 Affinda actions to the runtime in a format your agent can reliably use. | 105 tools for Affinda are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Affinda 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 Affinda in the browser, and the 105 tools above work from chat. There is no SDK and no config file, and the Affinda 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 Affinda skill but can't call the tools The ClawHub skill teaches OpenClaw about Affinda, but the calls run through the ClawLink plugin and your connected account. Make sure Affinda 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 Affinda 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 Affinda tools Affinda 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 Affinda 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. ### Affinda 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 Affinda has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Affinda integration? Yes. ClawLink is the fastest way to connect OpenClaw to Affinda: link your Affinda account once in the browser and OpenClaw can call the Affinda API through 105 ready-made tools — no custom code or token handling. ### How do I add Affinda to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Affinda skill from ClawHub, then you click Connect in the dashboard to authorize Affinda. OpenClaw calls the tools from the next message — no config files, and the Affinda key you paste is stored server-side instead of in your environment. ### How long does it take to connect Affinda to OpenClaw? About two minutes. Sign in, click Connect next to Affinda in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Affinda 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 Affinda working from chat. ### OpenClaw installed the Affinda skill but can't call the tools The ClawHub skill teaches OpenClaw about Affinda, but the calls run through the ClawLink plugin and your connected account. Make sure Affinda 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. - [Connect 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. - [ElevenLabs](https://claw-link.dev/openclaw/elevenlabs) — Generate speech and voice cloning