# How to connect Taggun to OpenClaw (paste one key, 14 tools) > Connect Taggun to OpenClaw with ClawLink: paste your Taggun key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/taggun The usual route to Taggun 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 Taggun setup: install one ClawHub skill, connect Taggun in the browser, and OpenClaw can call real Taggun 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 Taggun. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Taggun** — 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 taggun # connect Taggun (browser OAuth) npx -y @useclawlink/cli actions taggun # list available actions npx -y @useclawlink/cli run taggun --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 Taggun in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Taggun API key once. Verify the connection by asking OpenClaw: > Use Taggun to export known merchants 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 Taggun is connected in the dashboard, that agent calls the same 14 Taggun 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). ## Taggun MCP for OpenClaw Looking for a Taggun MCP server for OpenClaw? ClawLink connects Taggun to OpenClaw and exposes 14 Taggun 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 Taggun integration](https://claw-link.dev/hermes/taggun) works the same way. ## What the OpenClaw Taggun integration can do 14 Taggun tools are ready for OpenClaw once the account is connected. ### All 14 Taggun tools for OpenClaw | Tool | What it does | |---|---| | **Export known merchants** `taggun_export_known_merchants` | Export the complete list of known merchants used for merchant name normalization in Taggun | | **Export known product codes** `taggun_export_known_product_codes` | Export the complete list of known product codes used for product normalization and matching in | | **Export product categories** `taggun_export_product_categories` | Export a list of product categories and descriptions used for product categorization in CSV | | **Generate merchants CSV** `taggun_generate_merchants_csv` | Generate a CSV file with mock merchant data for testing purposes | | **Transcribe receipt encoded simple** `taggun_transcribe_receipt_encoded_simple` | Extract structured data from a receipt or invoice using base64 encoded image data | | **Transcribe receipt encoded verbose** `taggun_transcribe_receipt_encoded_verbose` | Transcribe a receipt using base64 encoded image in JSON payload and return detailed results | | **Transcribe receipt file simple** `taggun_transcribe_receipt_file_simple` | Upload a receipt or invoice image file and extract basic data including merchant name, total | | **URL** `taggun_url` | Extract structured data from a receipt or invoice image using OCR | | **URL validation** `taggun_url_validation` | Extract and validate receipt data from a URL | | **URL verbose** `taggun_url_verbose` | Process a receipt or invoice from a URL for detailed data extraction | | **Add merchant name** `taggun_add_merchant_name` | Add a merchant name keyword to your account's model for predicting merchant names | | **Import known merchants** `taggun_import_known_merchants` | Import a list of merchant names and addresses to normalize and match in CSV or TSV format | | **Import known product codes** `taggun_import_known_product_codes` | Import a list of product codes in CSV or TSV format for normalization and matching | | **Import product categories** `taggun_import_product_categories` | Import a list of product categories and descriptions for product categorization | ## Example prompts **Export Known Merchants** > Use Taggun to export known merchants and walk me through the result in plain English. **Export Known Product Codes** > Use Taggun to export known product codes and walk me through the result in plain English. **Export Product Categories** > Use Taggun to export product categories and walk me through the result in plain English. **Generate Merchants Csv** > Use Taggun to generate merchants csv 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 Taggun working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Taggun API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Taggun 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 Taggun. | 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 Taggun actions to the runtime in a format your agent can reliably use. | 14 tools for Taggun are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Taggun 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 Taggun in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Taggun 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 Taggun skill but can't call the tools The ClawHub skill teaches OpenClaw about Taggun, but the calls run through the ClawLink plugin and your connected account. Make sure Taggun 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 Taggun 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 Taggun tools Taggun 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 Taggun 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. ### Taggun 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 Taggun has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Taggun integration? Yes. ClawLink is the fastest way to connect OpenClaw to Taggun: link your Taggun account once in the browser and OpenClaw can call the Taggun API through 14 ready-made tools — no custom code or token handling. ### How do I add Taggun to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Taggun skill from ClawHub, then you click Connect in the dashboard to authorize Taggun. OpenClaw calls the tools from the next message — no config files, and the Taggun key you paste is stored server-side instead of in your environment. ### How long does it take to connect Taggun to OpenClaw? About two minutes. Sign in, click Connect next to Taggun in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Taggun 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 Taggun working from chat. ### OpenClaw installed the Taggun skill but can't call the tools The ClawHub skill teaches OpenClaw about Taggun, but the calls run through the ClawLink plugin and your connected account. Make sure Taggun 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 DataRobot integration](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. - [Chatbotkit tools](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. - [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.