# How to connect Goody to OpenClaw (paste one key, 13 tools)

> Connect Goody to OpenClaw with ClawLink: paste your Goody key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/goody

The usual route to Goody 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 Goody setup: install one ClawHub skill, connect Goody in the browser, and OpenClaw can call real Goody 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 Goody.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Goody** — 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 goody  # connect Goody (browser OAuth)
npx -y @useclawlink/cli actions goody  # list available actions
npx -y @useclawlink/cli run goody <action> --input '<json>'  # 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 Goody in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Goody API key once.

Verify the connection by asking OpenClaw:

> Use Goody to calculate price for order batch 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 Goody is connected in the dashboard, that agent calls the same 13 Goody 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).

## Goody MCP for OpenClaw

Looking for a Goody MCP server for OpenClaw? ClawLink connects Goody to OpenClaw and exposes 13 Goody 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 Goody integration](https://claw-link.dev/hermes/goody) works the same way.

## What the OpenClaw Goody integration can do

13 Goody tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 13.

### 12 of 13 Goody tools for OpenClaw

| Tool | What it does |
|---|---|
| **Calculate price for order batch** `goody_calculate_price_for_order_batch` | Calculate price estimate for an order batch before creation |
| **List all active cards** `goody_list_all_active_cards` | List all active digital greeting cards |
| **List all active products** `goody_list_all_active_products` | List all active products |
| **List all order batches** `goody_list_all_order_batches` | List all order batches |
| **List all orders** `goody_list_all_orders` | Retrieves a paginated list of all orders across all order batches in your Goody account |
| **List all payment methods** `goody_list_all_payment_methods` | Retrieves all saved payment methods for the authenticated account |
| **List all workspaces** `goody_list_all_workspaces` | List all workspaces |
| **List collections** `goody_list_collections` | List all collections across accessible workspaces |
| **List order activities** `goody_list_order_activities` | List all order activities (events) in your workspace |
| **Retrieve current user** `goody_retrieve_current_user` | Retrieve the current authenticated user's profile information from Goody API |
| **Retrieve product** `goody_retrieve_product` | Retrieve details of a specific product by its ID |
| **Create webhook** `goody_create_webhook` | Create a webhook endpoint to receive notifications about order events |

## Example prompts

**Calculate Price For Order Batch**

> Use Goody to calculate price for order batch and walk me through the result in plain English.

**List All Active Cards**

> List the relevant items in Goody, group them by priority, and recommend what OpenClaw should do next.

**List All Active Products**

> List the relevant items in Goody, group them by priority, and recommend what OpenClaw should do next.

**List All Order Batches**

> List the relevant items in Goody, group them by priority, and recommend what OpenClaw should do next.

## 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 Goody working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Goody API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Goody 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 Goody. | 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 Goody actions to the runtime in a format your agent can reliably use. | 13 tools for Goody are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Goody 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 Goody in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Goody 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 Goody skill but can't call the tools
The ClawHub skill teaches OpenClaw about Goody, but the calls run through the ClawLink plugin and your connected account. Make sure Goody 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 Goody 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 Goody tools
Goody 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 Goody 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.

### Goody 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 Goody has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Goody integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Goody: link your Goody account once in the browser and OpenClaw can call the Goody API through 13 ready-made tools — no custom code or token handling.

### How do I add Goody to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Goody skill from ClawHub, then you click Connect in the dashboard to authorize Goody. OpenClaw calls the tools from the next message — no config files, and the Goody key you paste is stored server-side instead of in your environment.

### How long does it take to connect Goody to OpenClaw?
About two minutes. Sign in, click Connect next to Goody in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Goody 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 Goody working from chat.

### OpenClaw installed the Goody skill but can't call the tools
The ClawHub skill teaches OpenClaw about Goody, but the calls run through the ClawLink plugin and your connected account. Make sure Goody 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.
- [Wix tools](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings
- [OpenClaw Baselinker integration](https://claw-link.dev/openclaw/baselinker) — BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.
