ClawLink

How to connect Taggun to OpenClaw

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.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Taggun
Taggun
TaggunAPI KEYMCP

Taggun is an AI-powered receipt OCR API that extracts structured data from receipt and invoice images in real-time.. Once connected, OpenClaw can read and act on Taggun from chat — pairing, token refresh, and tool wiring handled for you.

14 tools

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. 1

    Install the plugin

    Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:

    openclaw plugins install clawhub:clawlink-plugin
  2. 2

    Connect Taggun

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Taggun?"

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:

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 — 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:

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.

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, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Taggun integration 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

ToolWhat it does
Export known merchants taggun_export_known_merchantsExport the complete list of known merchants used for merchant name normalization in Taggun
Export known product codes taggun_export_known_product_codesExport the complete list of known product codes used for product normalization and matching in
Export product categories taggun_export_product_categoriesExport a list of product categories and descriptions used for product categorization in CSV
Generate merchants CSV taggun_generate_merchants_csvGenerate a CSV file with mock merchant data for testing purposes
Transcribe receipt encoded simple taggun_transcribe_receipt_encoded_simpleExtract structured data from a receipt or invoice using base64 encoded image data
Transcribe receipt encoded verbose taggun_transcribe_receipt_encoded_verboseTranscribe a receipt using base64 encoded image in JSON payload and return detailed results
Transcribe receipt file simple taggun_transcribe_receipt_file_simpleUpload a receipt or invoice image file and extract basic data including merchant name, total
URL taggun_urlExtract structured data from a receipt or invoice image using OCR
URL validation taggun_url_validationExtract and validate receipt data from a URL
URL verbose taggun_url_verboseProcess a receipt or invoice from a URL for detailed data extraction
Add merchant name taggun_add_merchant_nameAdd a merchant name keyword to your account's model for predicting merchant names
Import known merchants taggun_import_known_merchantsImport a list of merchant names and addresses to normalize and match in CSV or TSV format
Import known product codes taggun_import_known_product_codesImport a list of product codes in CSV or TSV format for normalization and matching
Import product categories taggun_import_product_categoriesImport a list of product categories and descriptions for product categorization

Try it: find the Taggun tool you need

Browse the 14 Taggun tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Use Taggun to export known merchants and walk me through the result in plain English.

Use Taggun to export known product codes and walk me through the result in plain English.

Use Taggun to export product categories and walk me through the result in plain English.

Use Taggun to generate merchants csv and walk me through the result in plain English.

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.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou 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.

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 comparison.

Troubleshooting

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.

FAQ

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.