# How to connect Missive to OpenClaw (paste one key, 40 tools)

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

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

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

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

Verify the connection by asking OpenClaw:

> Pull the relevant data from Missive, 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 Missive is connected in the dashboard, that agent calls the same 40 Missive 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).

## Missive MCP for OpenClaw

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

## What the OpenClaw Missive integration can do

40 Missive 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 40.

### 30 of 40 Missive tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get analytics report** `missive_get_analytics_report` | Fetch a completed analytics report using its ID |
| **Get contact** `missive_get_contact` | Fetch a specific contact using the contact ID |
| **Get conversation** `missive_get_conversation` | Fetch full conversation metadata (assignees/users/labels/team/org) for a specific conversation |
| **Get conversation messages** `missive_get_conversation_messages` | List messages belonging to a Missive conversation (newest first) |
| **Get message** `missive_get_message` | Fetch full message details including headers, HTML body, and attachments |
| **Get response** `missive_get_response` | Fetch a specific saved response using the response ID |
| **Get task** `missive_get_task` | Get a single task by ID with full details including assignees, team, and conversation info |
| **List contact books** `missive_list_contact_books` | List contact books the authenticated user has access to |
| **List contact groups** `missive_list_contact_groups` | List contact groups or organizations linked to a contact book |
| **List contacts** `missive_list_contacts` | List contacts from a contact book |
| **List conversation comments** `missive_list_conversation_comments` | List comments in a Missive conversation ordered from newest to oldest |
| **List conversation drafts** `missive_list_conversation_drafts` | List draft messages in a Missive conversation (newest first) |
| **List conversation posts** `missive_list_conversation_posts` | List posts in a Missive conversation ordered by newest first |
| **List conversations** `missive_list_conversations` | List conversations visible to the authenticated user ordered by newest activity first |
| **List messages** `missive_list_messages` | Fetch messages matching an email Message-ID header |
| **List organizations** `missive_list_organizations` | List organizations the authenticated user is part of |
| **List responses** `missive_list_responses` | List saved responses (canned responses/templates) for the authenticated user |
| **List shared labels** `missive_list_shared_labels` | List shared labels (organization-level labels) available to the authenticated user |
| **List tasks** `missive_list_tasks` | List tasks accessible to the authenticated user |
| **List teams** `missive_list_teams` | List all teams |
| **List users** `missive_list_users` | List all users |
| **Create analytics report** `missive_create_analytics_report` | Create an analytics report |
| **Create contacts** `missive_create_contacts` | Create one or more contacts in a Missive contact book |
| **Create draft** `missive_create_draft` | Create a new draft in Missive |
| **Create post** `missive_create_post` | Create a post in a Missive conversation |
| **Create response** `missive_create_response` | Create one or more canned responses (templates) in Missive |
| **Create shared label** `missive_create_shared_label` | Create one or more shared labels at the organization level |
| **Create task** `missive_create_task` | Create a task in Missive |
| **Create team** `missive_create_team` | Create a new team in an organization |
| **Create webhook** `missive_create_webhook` | Create a webhook subscription |

## Example prompts

**Get Analytics Report**

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

**Get Contact**

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

**Get Conversation**

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

**Get Conversation Messages**

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

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

## ClawLink vs. Composio

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

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

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

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

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

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

### OpenClaw installed the Missive skill but can't call the tools
The ClawHub skill teaches OpenClaw about Missive, but the calls run through the ClawLink plugin and your connected account. Make sure Missive 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 ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing
- [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.
- [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences