# How to connect Digital Humani to OpenClaw (paste one key, 7 tools) > Connect Digital Humani to OpenClaw with ClawLink: paste your Digital Humani key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/digital-humani The usual route to Digital Humani 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 Digital Humani setup: install one ClawHub skill, connect Digital Humani in the browser, and OpenClaw can call real Digital Humani 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 Digital Humani. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Digital Humani** — 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 digital-humani # connect Digital Humani (browser OAuth) npx -y @useclawlink/cli actions digital-humani # list available actions npx -y @useclawlink/cli run digital-humani --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 Digital Humani in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Digital Humani API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Digital Humani, 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 Digital Humani is connected in the dashboard, that agent calls the same 7 Digital Humani 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). ## Digital Humani MCP for OpenClaw Looking for a Digital Humani MCP server for OpenClaw? ClawLink connects Digital Humani to OpenClaw and exposes 7 Digital Humani 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 Digital Humani integration](https://claw-link.dev/hermes/digital-humani) works the same way. ## What the OpenClaw Digital Humani integration can do 7 Digital Humani tools are ready for OpenClaw once the account is connected. ### All 7 Digital Humani tools for OpenClaw | Tool | What it does | |---|---| | **Get current user and enterprise** `digital_humani_get_current_user_and_enterprise` | Return the authenticated Digital Humani user and that user's enterprise details, including the | | **Get enterprise tree count** `digital_humani_get_enterprise_tree_count` | Count trees for an enterprise across all time, one calendar month, or an inclusive date range | | **Get project** `digital_humani_get_project` | Return detailed information for one reforestation project, including whether it is active and | | **Get tree request** `digital_humani_get_tree_request` | Retrieve a tree-planting request by the UUID returned when it was created | | **Get user tree count** `digital_humani_get_user_tree_count` | Count trees attributed to an exact end-user identifier within an enterprise | | **List projects** `digital_humani_list_projects` | List reforestation project summaries and IDs | | **Plant trees** `digital_humani_plant_trees` | CHARGEABLE PRODUCTION PURCHASE: create a real tree-planting request at $1 per tree | ## Example prompts **Get Current User And Enterprise** > Pull the relevant data from Digital Humani, summarize it in plain English, and point out anything that needs attention. **Get Enterprise Tree Count** > Pull the relevant data from Digital Humani, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from Digital Humani, summarize it in plain English, and point out anything that needs attention. **Get Tree Request** > Pull the relevant data from Digital Humani, 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 Digital Humani working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Digital Humani API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Digital Humani 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 Digital Humani. | 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 Digital Humani actions to the runtime in a format your agent can reliably use. | 7 tools for Digital Humani are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Digital Humani 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 Digital Humani in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Digital Humani 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 Digital Humani skill but can't call the tools The ClawHub skill teaches OpenClaw about Digital Humani, but the calls run through the ClawLink plugin and your connected account. Make sure Digital Humani 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 Digital Humani 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 Digital Humani tools Digital Humani 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 Digital Humani 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. ### Digital Humani 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 Digital Humani has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Digital Humani integration? Yes. ClawLink is the fastest way to connect OpenClaw to Digital Humani: link your Digital Humani account once in the browser and OpenClaw can call the Digital Humani API through 7 ready-made tools — no custom code or token handling. ### How do I add Digital Humani to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Digital Humani skill from ClawHub, then you click Connect in the dashboard to authorize Digital Humani. OpenClaw calls the tools from the next message — no config files, and the Digital Humani key you paste is stored server-side instead of in your environment. ### How long does it take to connect Digital Humani to OpenClaw? About two minutes. Sign in, click Connect next to Digital Humani in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Digital Humani 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 Digital Humani working from chat. ### OpenClaw installed the Digital Humani skill but can't call the tools The ClawHub skill teaches OpenClaw about Digital Humani, but the calls run through the ClawLink plugin and your connected account. Make sure Digital Humani 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](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [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.