# How to connect PandaDoc to Hermes Agent (paste one key, 14 tools) > Connect PandaDoc to Hermes with ClawLink: paste your PandaDoc key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/pandadoc Most guides for giving Hermes Agent PandaDoc access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical PandaDoc setup: pair once in the browser and your always-on Hermes agent can act on PandaDoc for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Hermes to PandaDoc. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect PandaDoc** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 pandadoc # connect PandaDoc (browser OAuth) npx -y @useclawlink/cli actions pandadoc # list available actions npx -y @useclawlink/cli run pandadoc --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect PandaDoc in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PandaDoc API key once. Verify the connection by asking Hermes: > Create it in PandaDoc for me, then confirm the important fields before you finish. ### Using a different agent? The Hermes 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 PandaDoc is connected in the dashboard, that agent calls the same 14 PandaDoc 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). ## PandaDoc MCP for Hermes Looking for a PandaDoc MCP server for Hermes Agent? ClawLink connects PandaDoc to Hermes Agent and exposes 14 PandaDoc 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 OpenClaw instead? The [OpenClaw PandaDoc integration](https://claw-link.dev/openclaw/pandadoc) works the same way. ## What the Hermes Agent PandaDoc integration can do 14 PandaDoc tools are ready for Hermes Agent once the account is connected. The 12 below are the ones people reach for most; your agent can call all 14. ### 12 of 14 PandaDoc tools for Hermes | Tool | What it does | |---|---| | **Create document from file** `pandadoc_create_document_from_file` | Create a document from a PDF, DOCX, or RTF file | | **Create or update contact** `pandadoc_create_or_update_contact` | Create or update a PandaDoc contact | | **Create template** `pandadoc_create_template` | Create a new template from a PDF or scratch | | **Get document details** `pandadoc_get_document_details` | Get detailed metadata for a document | | **List contacts** `pandadoc_list_contacts` | List all contacts in the workspace | | **List templates** `pandadoc_list_templates` | List all templates in the PandaDoc account | | **Get template details** `pandadoc_get_template_details` | Retrieves detailed information about a specific template by its ID | | **List document folders** `pandadoc_list_document_folders` | Retrieves a list of all document folders in PandaDoc | | **Create document attachment** `pandadoc_create_document_attachment` | Creates and adds an attachment to a PandaDoc document | | **Create folder** `pandadoc_create_folder` | Creates a new folder in PandaDoc to organize documents | | **Create webhook** `pandadoc_create_webhook` | Creates a new webhook subscription in PandaDoc to receive notifications about specific events | | **Move document to folder** `pandadoc_move_document_to_folder` | Allows users to move a document to a specific folder within their PandaDoc account | ## Example prompts **Create Document From File** > Create it in PandaDoc for me, then confirm the important fields before you finish. **Create Or Update Contact** > Create it in PandaDoc for me, then confirm the important fields before you finish. **Create Template** > Create it in PandaDoc for me, then confirm the important fields before you finish. **Get Document Details** > Pull the relevant data from PandaDoc, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want PandaDoc working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PandaDoc API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PandaDoc 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 PandaDoc. | 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 PandaDoc actions to the runtime in a format your agent can reliably use. | 14 tools for PandaDoc are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PandaDoc 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 Hermes Agent users instead. You install the plugin once, connect PandaDoc in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the PandaDoc 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. ### Hermes paired but still can't use PandaDoc Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect PandaDoc 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 PandaDoc tools PandaDoc 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 PandaDoc 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. ### PandaDoc 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 PandaDoc has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent PandaDoc integration? Yes. ClawLink is the fastest way to connect Hermes to PandaDoc: link your PandaDoc account once in the browser and Hermes Agent can call the PandaDoc API through 14 ready-made tools — no custom code or token handling. ### How do I connect PandaDoc to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect PandaDoc in the dashboard and Hermes can use it from the next message — no config files, and the PandaDoc key you paste is stored server-side instead of in your environment. ### How long does it take to connect PandaDoc to Hermes Agent? About two minutes. Sign in, click Connect next to PandaDoc in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring PandaDoc up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want PandaDoc working from chat. ### Hermes paired but still can't use PandaDoc Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [DocuSign tools](https://claw-link.dev/hermes/docusign) — Send, sign, and manage agreements and envelopes - [Hermes Trello integration](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Hermes Moco integration](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.