# How to connect Postgrid to OpenClaw (paste one key, 60 tools) > Connect Postgrid to OpenClaw with ClawLink: paste your Postgrid 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/postgrid The usual route to Postgrid 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 Postgrid setup: install one ClawHub skill, connect Postgrid in the browser, and OpenClaw can call real Postgrid 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 Postgrid. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Postgrid** — 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 postgrid # connect Postgrid (browser OAuth) npx -y @useclawlink/cli actions postgrid # list available actions npx -y @useclawlink/cli run postgrid --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 Postgrid in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Postgrid API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Postgrid, 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 Postgrid is connected in the dashboard, that agent calls the same 60 Postgrid 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). ## Postgrid MCP for OpenClaw Looking for a Postgrid MCP server for OpenClaw? ClawLink connects Postgrid to OpenClaw and exposes 60 Postgrid 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 Postgrid integration](https://claw-link.dev/hermes/postgrid) works the same way. ## What the OpenClaw Postgrid integration can do 60 Postgrid 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 Postgrid tools for OpenClaw | Tool | What it does | |---|---| | **Get bank account** `postgrid_get_bank_account` | Retrieve a bank account | | **Get box** `postgrid_get_box` | Retrieve a specific box order by ID | | **Get cheque** `postgrid_get_cheque` | Retrieve a specific cheque by ID | | **Get contact** `postgrid_get_contact` | Retrieve a contact | | **Get letter** `postgrid_get_letter` | Retrieve a letter | | **Get postcard** `postgrid_get_postcard` | Retrieve a specific postcard by ID | | **Get return envelope** `postgrid_get_return_envelope` | Retrieve a return envelope | | **Get return envelope order** `postgrid_get_return_envelope_order` | Retrieve a specific return envelope order | | **Get template** `postgrid_get_template` | Retrieve a template | | **Get tracker** `postgrid_get_tracker` | Retrieve a tracker | | **Get webhook** `postgrid_get_webhook` | Retrieve details of a specific webhook by its ID | | **List bank accounts** `postgrid_list_bank_accounts` | List bank accounts | | **List boxes** `postgrid_list_boxes` | List box orders | | **List cheques** `postgrid_list_cheques` | List cheques with optional filters and pagination | | **List contacts** `postgrid_list_contacts` | List contacts | | **List events** `postgrid_list_events` | Retrieve a list of webhook events with optional pagination | | **List letters** `postgrid_list_letters` | List letters | | **List postal statements** `postgrid_list_postal_statements` | List all postal statements for billing and tracking purposes | | **List postcards** `postgrid_list_postcards` | Retrieve a list of postcards with optional filtering and pagination | | **List return envelope orders** `postgrid_list_return_envelope_orders` | List all return envelope orders for a specific return envelope | | **List return envelopes** `postgrid_list_return_envelopes` | List return envelopes | | **List self mailers** `postgrid_list_self_mailers` | List self-mailers | | **List sub organizations** `postgrid_list_sub_organizations` | List sub-organizations | | **List template editor sessions** `postgrid_list_template_editor_sessions` | List template editor sessions | | **List templates** `postgrid_list_templates` | List templates | | **List tracker visits** `postgrid_list_tracker_visits` | List all visits for a tracker | | **List trackers** `postgrid_list_trackers` | List all trackers | | **List webhook invocations** `postgrid_list_webhook_invocations` | List previous invocations of a webhook with response status codes | | **List webhooks** `postgrid_list_webhooks` | Retrieve a list of configured webhooks with optional filtering and pagination | | **Create bank account** `postgrid_create_bank_account` | Create a new bank account for print & mail service | ## Example prompts **Get Bank Account** > Pull the relevant data from Postgrid, summarize it in plain English, and point out anything that needs attention. **Get Box** > Pull the relevant data from Postgrid, summarize it in plain English, and point out anything that needs attention. **Get Cheque** > Pull the relevant data from Postgrid, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Postgrid, 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 Postgrid working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Postgrid API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Postgrid 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 Postgrid. | 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 Postgrid actions to the runtime in a format your agent can reliably use. | 60 tools for Postgrid are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Postgrid 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 Postgrid in the browser, and the 60 tools above work from chat. There is no SDK and no config file, and the Postgrid 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 Postgrid skill but can't call the tools The ClawHub skill teaches OpenClaw about Postgrid, but the calls run through the ClawLink plugin and your connected account. Make sure Postgrid 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 Postgrid 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 Postgrid tools Postgrid 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 Postgrid 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. ### Postgrid 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 Postgrid has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Postgrid integration? Yes. ClawLink is the fastest way to connect OpenClaw to Postgrid: link your Postgrid account once in the browser and OpenClaw can call the Postgrid API through 60 ready-made tools — no custom code or token handling. ### How do I add Postgrid to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Postgrid skill from ClawHub, then you click Connect in the dashboard to authorize Postgrid. OpenClaw calls the tools from the next message — no config files, and the Postgrid key you paste is stored server-side instead of in your environment. ### How long does it take to connect Postgrid to OpenClaw? About two minutes. Sign in, click Connect next to Postgrid in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Postgrid 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 Postgrid working from chat. ### OpenClaw installed the Postgrid skill but can't call the tools The ClawHub skill teaches OpenClaw about Postgrid, but the calls run through the ClawLink plugin and your connected account. Make sure Postgrid 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 - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.