# How to connect Planly to OpenClaw (paste one key, 15 tools)

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

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

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

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

Verify the connection by asking OpenClaw:

> Use Planly to complete ai prompt 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 Planly is connected in the dashboard, that agent calls the same 15 Planly 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).

## Planly MCP for OpenClaw

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

## What the OpenClaw Planly integration can do

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

### 13 of 15 Planly tools for OpenClaw

| Tool | What it does |
|---|---|
| **Complete AI prompt** `planly_complete_ai_prompt` | Complete a text prompt using AI |
| **Get AI credits** `planly_get_ai_credits` | Retrieve available AI credits left in a team |
| **Get team** `planly_get_team` | Retrieve detailed information about a specific team including permissions, limits, and |
| **List channels** `planly_list_channels` | List all social media channels connected to a team |
| **List media** `planly_list_media` | Retrieve a paginated list of media files in a team |
| **List schedule groups** `planly_list_schedule_groups` | Retrieve a list of schedule groups for a team with comprehensive filtering and pagination |
| **List schedules** `planly_list_schedules` | Retrieve a paginated list of schedules in a specified team |
| **List team users** `planly_list_team_users` | List all users that belong to a specific team |
| **List teams** `planly_list_teams` | Retrieve all teams that the authenticated user belongs to |
| **Create team** `planly_create_team` | Create a new team in Planly |
| **Edit team** `planly_edit_team` | Edit team details such as name in Planly |
| **Import media from URL** `planly_import_media_from_url` | Import media from a URL to your team |
| **Start media upload** `planly_start_media_upload` | Start the upload process for a media file |

## Example prompts

**Complete Ai Prompt**

> Use Planly to complete ai prompt and walk me through the result in plain English.

**Get Ai Credits**

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

**Get Team**

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

**List Channels**

> List the relevant items in Planly, 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 Planly working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

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

- [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing
- [Connect Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns.
- [Connect Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences
