# How to connect Fingertip to OpenClaw (paste one key, 60 tools)

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

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

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

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

Verify the connection by asking OpenClaw:

> Pull the relevant data from Fingertip, summarize it in plain English, and point out anything that needs attention.

### 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 Fingertip is connected in the dashboard, that agent calls the same 60 Fingertip 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).

## Fingertip MCP for OpenClaw

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

## What the OpenClaw Fingertip integration can do

60 Fingertip 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 60.

### 30 of 60 Fingertip tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get block** `fingertip_get_block` | Retrieve a specific block by its ID |
| **Get comprehensive site analytics** `fingertip_get_comprehensive_site_analytics` | Retrieve comprehensive analytics for a specific site |
| **Get invoice item** `fingertip_get_invoice_item` | Retrieve details of a specific invoice item by its ID |
| **Get page** `fingertip_get_page` | Retrieve a specific Fingertip page by its ID |
| **Get page theme** `fingertip_get_page_theme` | Retrieve the theme configuration for a specific page |
| **Get site** `fingertip_get_site` | Retrieve a specific Fingertip site by its UUID |
| **Get webhook** `fingertip_get_webhook` | Retrieve a specific webhook by ID with its related triggers |
| **Health check** `fingertip_health_check` | Verify API connectivity |
| **List blog posts** `fingertip_list_blog_posts` | List published blog posts for a specific site |
| **List bookings** `fingertip_list_bookings` | Retrieve a paginated list of bookings for a site with optional status filtering |
| **List event types** `fingertip_list_event_types` | List event types for a specific site |
| **List form responses** `fingertip_list_form_responses` | Retrieve form responses for a specific form template and site |
| **List form templates** `fingertip_list_form_templates` | Retrieve a paginated list of form templates |
| **List invoice items** `fingertip_list_invoice_items` | List invoice items for a specific Fingertip site |
| **List invoices** `fingertip_list_invoices` | Retrieve a paginated list of invoices for sites the user has access to |
| **List messages** `fingertip_list_messages` | Retrieve a paginated list of messages for a site |
| **List orders** `fingertip_list_orders` | Retrieve orders with basic information for a specific site |
| **List page blocks** `fingertip_list_page_blocks` | Retrieve all blocks associated with a specific page |
| **List page themes** `fingertip_list_page_themes` | Retrieve a paginated list of page themes |
| **List pages** `fingertip_list_pages` | List all pages for a specific Fingertip site |
| **List quotes** `fingertip_list_quotes` | List all quotes for a specific Fingertip site |
| **List sample bookings** `fingertip_list_sample_bookings` | Retrieve sample bookings for testing and development purposes |
| **List sample form responses** `fingertip_list_sample_form_responses` | Retrieve sample form responses for a specific form template |
| **List sample orders** `fingertip_list_sample_orders` | Retrieve sample orders for testing purposes |
| **List sample site contacts** `fingertip_list_sample_site_contacts` | Retrieve sample site contacts with basic information |
| **List site contacts** `fingertip_list_site_contacts` | Retrieve site contacts with basic contact information and engagement metrics |
| **List site invitations** `fingertip_list_site_invitations` | Retrieve a paginated list of invitations for a specific site |
| **List site memberships** `fingertip_list_site_memberships` | Retrieve a paginated list of site memberships |
| **List sites** `fingertip_list_sites` | Retrieve a paginated list of sites accessible by the API key |
| **List webhooks** `fingertip_list_webhooks` | Retrieve a paginated list of webhooks with optional filtering and sorting |

## Example prompts

**Get Block**

> Pull the relevant data from Fingertip, summarize it in plain English, and point out anything that needs attention.

**Get Comprehensive Site Analytics**

> Pull the relevant data from Fingertip, summarize it in plain English, and point out anything that needs attention.

**Get Invoice Item**

> Pull the relevant data from Fingertip, summarize it in plain English, and point out anything that needs attention.

**Get Page**

> Pull the relevant data from Fingertip, summarize it in plain English, and point out anything that needs attention.

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

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

## ClawLink vs. Composio

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

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

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

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

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

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

### OpenClaw installed the Fingertip skill but can't call the tools
The ClawHub skill teaches OpenClaw about Fingertip, but the calls run through the ClawLink plugin and your connected account. Make sure Fingertip 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

- [Cloudcart](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently.
- [Wix](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings
- [Baselinker](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.
