# How to connect eSignatures to OpenClaw (paste one key, 28 tools) > Connect eSignatures to OpenClaw with ClawLink: paste your eSignatures key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/esignatures The usual route to eSignatures 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 eSignatures setup: install one ClawHub skill, connect eSignatures in the browser, and OpenClaw can call real eSignatures 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 eSignatures. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect eSignatures** — 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 esignatures # connect eSignatures (browser OAuth) npx -y @useclawlink/cli actions esignatures # list available actions npx -y @useclawlink/cli run esignatures --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 eSignatures in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your eSignatures API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from eSignatures, 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 eSignatures is connected in the dashboard, that agent calls the same 28 eSignatures 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). ## eSignatures MCP for OpenClaw Looking for a eSignatures MCP server for OpenClaw? ClawLink connects eSignatures to OpenClaw and exposes 28 eSignatures 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 eSignatures integration](https://claw-link.dev/hermes/esignatures) works the same way. ## What the OpenClaw eSignatures integration can do 28 eSignatures tools are ready for OpenClaw once the account is connected. The 26 below are the ones people reach for most; your agent can call all 28. ### 26 of 28 eSignatures tools for OpenClaw | Tool | What it does | |---|---| | **Get contract** `esignatures_get_contract` | Get one contract's current status, details, signers, signer field values, and temporary | | **Get contract content** `esignatures_get_contract_content` | Return the Markdown content of one contract | | **Get contract placeholder fields** `esignatures_get_contract_placeholder_fields` | Return the current placeholder replacements for one contract | | **Get template** `esignatures_get_template` | Get one template's metadata, placeholder keys, and signer-field IDs | | **Get template content** `esignatures_get_template_content` | Return the Markdown content of one template | | **List template collaborators** `esignatures_list_template_collaborators` | Return all collaborators who can edit one template | | **List templates** `esignatures_list_templates` | Return all templates available to the connected account | | **Preview contract content update** `esignatures_preview_contract_content_update` | Preview the prospective Markdown from exact find-and-replace edits without mutating the contract | | **Preview template content update** `esignatures_preview_template_content_update` | Preview the prospective Markdown from exact find-and-replace edits without mutating the template | | **Add contract signer** `esignatures_add_contract_signer` | Add a signer to an editable contract without automatically sending a signature request | | **Add contract signers** `esignatures_add_contract_signers` | Add a non-empty list of signers to an editable contract by calling the provider's singular | | **Add template collaborator** `esignatures_add_template_collaborator` | Create a name-only collaborator who can edit a template | | **Create contract draft** `esignatures_create_contract_draft` | Create a test or production contract draft from a template or from ad-hoc Markdown, without | | **Create template** `esignatures_create_template` | Create a reusable Markdown contract template | | **Duplicate template** `esignatures_duplicate_template` | Duplicate a template with a new title plus optional placeholder replacements | | **Update contract content** `esignatures_update_contract_content` | Apply exact Markdown find-and-replace edits to a contract | | **Update contract placeholder fields** `esignatures_update_contract_placeholder_fields` | Update selected placeholder replacements on an unsigned contract | | **Update contract signer** `esignatures_update_contract_signer` | Update selected contact, delivery, authentication, or redirect details for a signer without | | **Update template** `esignatures_update_template` | Update a template's title and/or labels without changing its Markdown content | | **Update template content** `esignatures_update_template_content` | Apply exact Markdown find-and-replace edits to a template | | **Create and send contract** `esignatures_create_and_send_contract` | Create a contract from a template or from ad-hoc Markdown and immediately send signature | | **Invite template collaborator** `esignatures_invite_template_collaborator` | Invite a collaborator to edit a template | | **Remove template collaborator** `esignatures_remove_template_collaborator` | Remove a collaborator's permission to edit a template | | **Resend sign request** `esignatures_resend_sign_request` | Resend a signature request to one signer | | **Send draft contract** `esignatures_send_draft_contract` | Send an existing draft to its signers | | **Withdraw contract** `esignatures_withdraw_contract` | Irreversibly withdraw an active unsigned contract so it can no longer be signed | ## Example prompts **Get Contract** > Pull the relevant data from eSignatures, summarize it in plain English, and point out anything that needs attention. **Get Contract Content** > Pull the relevant data from eSignatures, summarize it in plain English, and point out anything that needs attention. **Get Contract Placeholder Fields** > Pull the relevant data from eSignatures, summarize it in plain English, and point out anything that needs attention. **Get Template** > Pull the relevant data from eSignatures, 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 eSignatures working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the eSignatures API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected eSignatures 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 eSignatures. | 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 eSignatures actions to the runtime in a format your agent can reliably use. | 28 tools for eSignatures are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes eSignatures 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 eSignatures in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the eSignatures 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 eSignatures skill but can't call the tools The ClawHub skill teaches OpenClaw about eSignatures, but the calls run through the ClawLink plugin and your connected account. Make sure eSignatures 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 eSignatures 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 eSignatures tools eSignatures 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 eSignatures 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. ### eSignatures 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 eSignatures has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw eSignatures integration? Yes. ClawLink is the fastest way to connect OpenClaw to eSignatures: link your eSignatures account once in the browser and OpenClaw can call the eSignatures API through 28 ready-made tools — no custom code or token handling. ### How do I add eSignatures to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink eSignatures skill from ClawHub, then you click Connect in the dashboard to authorize eSignatures. OpenClaw calls the tools from the next message — no config files, and the eSignatures key you paste is stored server-side instead of in your environment. ### How long does it take to connect eSignatures to OpenClaw? About two minutes. Sign in, click Connect next to eSignatures in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring eSignatures 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 eSignatures working from chat. ### OpenClaw installed the eSignatures skill but can't call the tools The ClawHub skill teaches OpenClaw about eSignatures, but the calls run through the ClawLink plugin and your connected account. Make sure eSignatures 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 GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](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.