# How to connect Magnetic to OpenClaw (paste one key, 14 tools)

> Connect Magnetic to OpenClaw with ClawLink: paste your Magnetic 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/magnetic

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

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

Verify the connection by asking OpenClaw:

> Use Magnetic to clients get current followups 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 Magnetic is connected in the dashboard, that agent calls the same 14 Magnetic 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).

## Magnetic MCP for OpenClaw

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

## What the OpenClaw Magnetic integration can do

14 Magnetic tools are ready for OpenClaw once the account is connected.

### All 14 Magnetic tools for OpenClaw

| Tool | What it does |
|---|---|
| **Clients get current followups** `magnetic_clients_get_current_followups` | Retrieve upcoming follow-ups assigned to the authenticated user |
| **Clients search contacts** `magnetic_clients_search_contacts` | Search contacts by field or client ID |
| **Get contact tags** `magnetic_get_contact_tags` | Get all tags associated with a contact |
| **Get grouping by ID** `magnetic_get_grouping_by_id` | Retrieve details for a specific grouping (opportunity/job) by its ID |
| **Get grouping statuses** `magnetic_get_grouping_statuses` | Retrieve the list of statuses for signed groupings |
| **Get grouping tags** `magnetic_get_grouping_tags` | Retrieve tags associated with any groupings owned by the company |
| **Get opportunity statuses** `magnetic_get_opportunity_statuses` | Retrieve opportunity statuses |
| **Get task** `magnetic_get_task` | Retrieve a task by its ID |
| **Get user by ID** `magnetic_get_user_by_id` | Retrieve details for a specific Magnetic user by their ID |
| **Get users** `magnetic_get_users` | Retrieve the list of all users in the authenticated user's company |
| **List companies** `magnetic_list_companies` | Retrieve all companies from the Magnetic HQ account |
| **Tasks get grouping custom field definitions** `magnetic_tasks_get_grouping_custom_field_definitions` | Retrieve all custom field definitions for groupings |
| **Create grouping** `magnetic_create_grouping` | Create a new opportunity or job (grouping) in Magnetic HQ |
| **Create task** `magnetic_create_task` | Create a new task in Magnetic HQ |

## Example prompts

**Clients Get Current Followups**

> Use Magnetic to clients get current followups and walk me through the result in plain English.

**Clients Search Contacts**

> Search Magnetic for what I need, summarize the results, and tell me the next best action.

**Get Contact Tags**

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

**Get Grouping By Id**

> Pull the relevant data from Magnetic, 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 Magnetic working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

### OpenClaw installed the Magnetic skill but can't call the tools
The ClawHub skill teaches OpenClaw about Magnetic, but the calls run through the ClawLink plugin and your connected account. Make sure Magnetic 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 HubSpot integration](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines
- [OpenClaw CentralStationCRM integration](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships.
- [Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows
