# How to connect Postmark to OpenClaw (paste one key, 46 tools) > Connect Postmark to OpenClaw with ClawLink: paste your Postmark key once and 46 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/postmark The usual route to Postmark 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 Postmark setup: install one ClawHub skill, connect Postmark in the browser, and OpenClaw can call real Postmark actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/postmark ## Setup It takes three steps to connect OpenClaw to Postmark. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Postmark** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 postmark # connect Postmark (browser OAuth) npx -y @useclawlink/cli actions postmark # list available actions npx -y @useclawlink/cli run postmark --input '' # 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 Postmark in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Postmark API key once. Verify the connection by asking OpenClaw: > Use Postmark to check spam score 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 Postmark is connected in the dashboard, that agent calls the same 46 Postmark 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). ## Postmark MCP for OpenClaw Looking for a Postmark MCP server for OpenClaw? ClawLink connects Postmark to OpenClaw and exposes 46 Postmark 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 Postmark integration](https://claw-link.dev/hermes/postmark) works the same way. ## What the OpenClaw Postmark integration can do 46 Postmark 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 46. ### 30 of 46 Postmark tools for OpenClaw | Tool | What it does | |---|---| | **Check spam score** `postmark_check_spam_score` | Check email spam score in Postmark | | **Create inbound rule** `postmark_create_inbound_rule` | Create a Postmark inbound rule | | **Create message stream** `postmark_create_message_stream` | Create a Postmark message stream | | **Create suppressions** `postmark_create_suppressions` | Create Postmark suppressions | | **Create template** `postmark_create_template` | Create a Postmark template | | **Create webhook** `postmark_create_webhook` | Create a Postmark webhook | | **Edit template** `postmark_edit_template` | Edit a Postmark template | | **Get bounce counts** `postmark_get_bounce_counts` | Get Postmark bounce counts | | **Get bounces** `postmark_get_bounces` | List Postmark bounces | | **Get browser platform usage** `postmark_get_browser_platform_usage` | Get Postmark browser and platform usage | | **Get click counts** `postmark_get_click_counts` | Get Postmark click counts | | **Get delivery stats** `postmark_get_delivery_stats` | Get Postmark delivery statistics | | **Get email open counts** `postmark_get_email_open_counts` | Get Postmark email open counts | | **Get message stream** `postmark_get_message_stream` | Get a Postmark message stream | | **Get browser usage** `postmark_get_browser_usage` | Retrieve browser usage statistics for clicked links | | **Get clicks by browser family** `postmark_get_clicks_by_browser_family` | Retrieve click statistics grouped by browser family | | **Get clicks by location** `postmark_get_clicks_by_location` | Get an overview of which part of the email links were clicked from (HTML or Text) | | **Get email client usage** `postmark_get_email_client_usage` | Retrieve statistics on email clients used to open emails | | **Get opens by platform** `postmark_get_opens_by_platform` | Retrieve email open statistics by platform type | | **Get outbound overview** `postmark_get_outbound_overview` | Retrieve outbound email statistics overview | | **Get sent counts** `postmark_get_sent_counts` | Retrieve total count of emails sent out | | **Get server** `postmark_get_server` | Retrieve details of the current Postmark server | | **Get spam complaints** `postmark_get_spam_complaints` | Retrieve counts of spam complaints | | **Get template** `postmark_get_template` | Retrieve details of a specific template by its ID | | **Get tracked email counts** `postmark_get_tracked_email_counts` | Retrieve counts of emails with tracking enabled | | **Get webhook** `postmark_get_webhook` | Retrieve details of a specific webhook by its ID | | **List inbound rules** `postmark_list_inbound_rules` | List all inbound rules (triggers) configured for blocking senders | | **List message streams** `postmark_list_message_streams` | List all message streams for a Postmark server with optional type and archive filtering | | **List outbound message clicks** `postmark_list_outbound_message_clicks` | List clicks for outbound messages with filtering options | | **List outbound message opens** `postmark_list_outbound_message_opens` | Retrieve opens for outbound messages with filtering options | ## Example prompts **Check Spam Score** > Use Postmark to check spam score and walk me through the result in plain English. **Create Inbound Rule** > Create it in Postmark for me, then confirm the important fields before you finish. **Create Message Stream** > Create it in Postmark for me, then confirm the important fields before you finish. **Create Suppressions** > Create it in Postmark for me, then confirm the important fields before you finish. ## 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 Postmark working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Postmark API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Postmark 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 Postmark. | 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 Postmark actions to the runtime in a format your agent can reliably use. | 46 tools for Postmark are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Postmark 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 Postmark in the browser, and the 46 tools above work from chat. There is no SDK and no config file, and the Postmark 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 Postmark skill but can't call the tools The ClawHub skill teaches OpenClaw about Postmark, but the calls run through the ClawLink plugin and your connected account. Make sure Postmark 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 Postmark 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 Postmark tools Postmark 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 Postmark 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. ### Postmark 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 Postmark has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Postmark integration? Yes. ClawLink is the fastest way to connect OpenClaw to Postmark: link your Postmark account once in the browser and OpenClaw can call the Postmark API through 46 ready-made tools — no custom code or token handling. ### How do I add Postmark to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Postmark skill from ClawHub, then you click Connect in the dashboard to authorize Postmark. OpenClaw calls the tools from the next message — no config files, and the Postmark key you paste is stored server-side instead of in your environment. ### How long does it take to connect Postmark to OpenClaw? About two minutes. Sign in, click Connect next to Postmark in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Postmark 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 Postmark working from chat. ### OpenClaw installed the Postmark skill but can't call the tools The ClawHub skill teaches OpenClaw about Postmark, but the calls run through the ClawLink plugin and your connected account. Make sure Postmark 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 - [SendGrid](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Dialpad tools](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions