# How to connect Baselinker to OpenClaw (paste one key, 106 tools) > Connect Baselinker to OpenClaw with ClawLink: paste your Baselinker key once and 106 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/baselinker The usual route to Baselinker 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 Baselinker setup: install one ClawHub skill, connect Baselinker in the browser, and OpenClaw can call real Baselinker 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/baselinker ## Setup It takes three steps to connect OpenClaw to Baselinker. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Baselinker** — 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 baselinker # connect Baselinker (browser OAuth) npx -y @useclawlink/cli actions baselinker # list available actions npx -y @useclawlink/cli run baselinker --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 Baselinker in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Baselinker API key once. Verify the connection by asking OpenClaw: > Use Baselinker to add inventory 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 Baselinker is connected in the dashboard, that agent calls the same 106 Baselinker 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). ## Baselinker MCP for OpenClaw Looking for a Baselinker MCP server for OpenClaw? ClawLink connects Baselinker to OpenClaw and exposes 106 Baselinker 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 Baselinker integration](https://claw-link.dev/hermes/baselinker) works the same way. ## What the OpenClaw Baselinker integration can do 106 Baselinker 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 106. ### 30 of 106 Baselinker tools for OpenClaw | Tool | What it does | |---|---| | **Add inventory** `baselinker_add_inventory` | Add or update a BaseLinker catalog (inventory) | | **Add inventory category** `baselinker_add_inventory_category` | Add or update a category in the BaseLinker catalog | | **Add inventory document** `baselinker_add_inventory_document` | Create a new inventory document in BaseLinker storage | | **Add inventory manufacturer** `baselinker_add_inventory_manufacturer` | Add or update a manufacturer in the BaseLinker catalog | | **Get connect integration contractors** `baselinker_get_connect_integration_contractors` | Retrieve a list of contractors connected to a selected Base Connect integration | | **Get connect integrations** `baselinker_get_connect_integrations` | Retrieve a list of all Base Connect integrations on this account | | **Get courier accounts** `baselinker_get_courier_accounts` | Retrieve the list of accounts connected to a given courier | | **Get courier fields** `baselinker_get_courier_fields` | Retrieve the form fields required for creating shipments with a specific courier | | **Get courier packages status history** `baselinker_get_courier_packages_status_history` | Retrieve the history of status changes for courier packages | | **Get couriers list** `baselinker_get_couriers_list` | Retrieve a list of available couriers from BaseLinker | | **Get external storage products quantity** `baselinker_get_external_storage_products_quantity` | Retrieve stock quantities from an external storage (shop/wholesaler) connected to BaseLinker | | **Get external storages list** `baselinker_get_external_storages_list` | Retrieve a list of external storages (shops, warehouses, wholesalers) connected to BaseLinker that can be referenced via API | | **Get inventories** `baselinker_get_inventories` | Retrieve a list of catalogs (inventories) available in the BaseLinker storage | | **Get inventory available text field keys** `baselinker_get_inventory_available_text_field_keys` | Retrieve a list of product text fields that can be overwritten for a specific integration | | **Get inventory categories** `baselinker_get_inventory_categories` | Retrieve a list of categories for a BaseLinker catalog | | **Get inventory document items** `baselinker_get_inventory_document_items` | Retrieve items from inventory documents in BaseLinker | | **Get inventory document series** `baselinker_get_inventory_document_series` | Retrieve available inventory document series | | **Get inventory documents** `baselinker_get_inventory_documents` | Retrieve a list of inventory documents | | **Get inventory extra fields** `baselinker_get_inventory_extra_fields` | Retrieve extra fields defined for BaseLinker catalog inventory items | | **Get inventory integrations** `baselinker_get_inventory_integrations` | Retrieve a list of integrations where text values in the catalog can be overwritten | | **Get inventory manufacturers** `baselinker_get_inventory_manufacturers` | Retrieve a list of manufacturers from the BaseLinker catalog | | **Get inventory payers** `baselinker_get_inventory_payers` | Retrieve a list of payers available in BaseLinker storage | | **Get inventory price groups** `baselinker_get_inventory_price_groups` | Retrieve price groups existing in BaseLinker storage | | **Get inventory printout templates** `baselinker_get_inventory_printout_templates` | Retrieve a list of all configured printout templates available for inventory (products) | | **Get inventory product logs** `baselinker_get_inventory_product_logs` | Retrieve a list of events related to product changes in the BaseLinker catalog | | **Get inventory products data** `baselinker_get_inventory_products_data` | Retrieve detailed data for selected products from the BaseLinker inventory | | **Get inventory products list** `baselinker_get_inventory_products_list` | Retrieve basic data of chosen products from BaseLinker catalogs | | **Get inventory products prices** `baselinker_get_inventory_products_prices` | Retrieve gross prices of products from BaseLinker inventories | | **Get inventory products stock** `baselinker_get_inventory_products_stock` | Retrieve stock data of products from BaseLinker catalogs | | **Get inventory purchase order items** `baselinker_get_inventory_purchase_order_items` | Retrieve items from a specific purchase order in BaseLinker | ## Example prompts **Add Inventory** > Use Baselinker to add inventory and walk me through the result in plain English. **Add Inventory Category** > Use Baselinker to add inventory category and walk me through the result in plain English. **Add Inventory Document** > Use Baselinker to add inventory document and walk me through the result in plain English. **Add Inventory Manufacturer** > Use Baselinker to add inventory manufacturer 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 Baselinker working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Baselinker API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Baselinker 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 Baselinker. | 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 Baselinker actions to the runtime in a format your agent can reliably use. | 106 tools for Baselinker are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Baselinker 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 Baselinker in the browser, and the 106 tools above work from chat. There is no SDK and no config file, and the Baselinker 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 Baselinker skill but can't call the tools The ClawHub skill teaches OpenClaw about Baselinker, but the calls run through the ClawLink plugin and your connected account. Make sure Baselinker 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 Baselinker 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 Baselinker tools Baselinker 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 Baselinker 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. ### Baselinker 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 Baselinker has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Baselinker integration? Yes. ClawLink is the fastest way to connect OpenClaw to Baselinker: link your Baselinker account once in the browser and OpenClaw can call the Baselinker API through 106 ready-made tools — no custom code or token handling. ### How do I add Baselinker to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Baselinker skill from ClawHub, then you click Connect in the dashboard to authorize Baselinker. OpenClaw calls the tools from the next message — no config files, and the Baselinker key you paste is stored server-side instead of in your environment. ### How long does it take to connect Baselinker to OpenClaw? About two minutes. Sign in, click Connect next to Baselinker in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Baselinker 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 Baselinker working from chat. ### OpenClaw installed the Baselinker skill but can't call the tools The ClawHub skill teaches OpenClaw about Baselinker, but the calls run through the ClawLink plugin and your connected account. Make sure Baselinker 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 - [OpenClaw Cloudcart integration](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently. - [Shippo](https://claw-link.dev/openclaw/shippo) — Generate shipping labels, track packages, and manage fulfillment - [Zoho Inventory](https://claw-link.dev/openclaw/zoho-inventory) — Manage stock levels, orders, warehouses, and fulfillment