# How to connect People Data Labs to OpenClaw (paste one key, 23 tools) > Connect People Data Labs to OpenClaw with ClawLink: paste your People Data Labs key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/peopledatalabs The usual route to People Data Labs 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 People Data Labs setup: install one ClawHub skill, connect People Data Labs in the browser, and OpenClaw can call real People Data Labs 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 People Data Labs. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect People Data Labs** — 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 peopledatalabs # connect People Data Labs (browser OAuth) npx -y @useclawlink/cli actions peopledatalabs # list available actions npx -y @useclawlink/cli run peopledatalabs --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 People Data Labs in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your People Data Labs API key once. Verify the connection by asking OpenClaw: > Use People Data Labs to clean company data 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 People Data Labs is connected in the dashboard, that agent calls the same 23 People Data Labs 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). ## People Data Labs MCP for OpenClaw Looking for a People Data Labs MCP server for OpenClaw? ClawLink connects People Data Labs to OpenClaw and exposes 23 People Data Labs 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 People Data Labs integration](https://claw-link.dev/hermes/peopledatalabs) works the same way. ## What the OpenClaw People Data Labs integration can do 23 People Data Labs tools are ready for OpenClaw once the account is connected. ### All 23 People Data Labs tools for OpenClaw | Tool | What it does | |---|---| | **Clean company data** `peopledatalabs_clean_company_data` | Cleans and standardizes company information based on a name, website, or profile URL; providing | | **Clean company post** `peopledatalabs_clean_company_post` | Clean and standardize company data using POST method | | **Clean location data** `peopledatalabs_clean_location_data` | Cleans and standardizes a raw, unformatted location string into a structured representation | | **Clean location post** `peopledatalabs_clean_location_post` | Clean and standardize location data using POST method | | **Clean school data** `peopledatalabs_clean_school_data` | Cleans and standardizes school information; provide at least one of the school's name, website | | **Clean school data post** `peopledatalabs_clean_school_data_post` | Clean and standardize school data using POST method | | **Enrich bulk company data** `peopledatalabs_enrich_bulk_company_data` | Enrich up to 100 companies in a single request using the Bulk Company Enrichment API | | **Enrich bulk person data** `peopledatalabs_enrich_bulk_person_data` | Enrich up to 100 person profiles in a single API request using the Bulk Person Enrichment API | | **Enrich company data** `peopledatalabs_enrich_company_data` | Enriches company data from People Data Labs with details like firmographics and employee counts | | **Enrich ip data** `peopledatalabs_enrich_ip_data` | Enriches an IP address with company, location, metadata, and person data from People Data Labs | | **Enrich job title data** `peopledatalabs_enrich_job_title_data` | Enhances a job title by providing additional contextual information and details | | **Enrich person data** `peopledatalabs_enrich_person_data` | Enriches person data using various identifiers; requires a primary ID (profile, email, phone | | **Enrich skill data** `peopledatalabs_enrich_skill_data` | Retrieves detailed, standardized information for a given skill by querying the People Data Labs | | **Get autocomplete suggestions** `peopledatalabs_get_autocomplete_suggestions` | Provides autocompletion suggestions for a specific field (e.g., company, skill, title) based on | | **Get autocomplete suggestions post** `peopledatalabs_get_autocomplete_suggestions_post` | Get autocompletion suggestions using POST method for complex query parameters | | **Get column details** `peopledatalabs_get_column_details` | Retrieves predefined enum values for a column name from `enum_mappings.json`; `is_enum` in the | | **Get schema** `peopledatalabs_get_schema` | Retrieves the schema, including field names, descriptions, and data types, for 'person' or | | **Get subject requests** `peopledatalabs_get_subject_requests` | Retrieve subject access requests for data privacy compliance | | **Identify person data** `peopledatalabs_identify_person_data` | Retrieves detailed profile information for an individual from People Data Labs (PDL), requiring | | **People search elastic** `peopledatalabs_people_search_elastic` | Searches for person profiles in the People Data Labs (PDL) database using an Elasticsearch | | **Query person changelog** `peopledatalabs_query_person_changelog` | Query the changelog of person records between two consecutive dataset versions | | **Search company elastic** `peopledatalabs_search_company_elastic` | Performs a search for company profiles within People Data Labs using a custom Elasticsearch | | **Search company post** `peopledatalabs_search_company_post` | Search and filter company records from the full Company Dataset using Elasticsearch or SQL | ## Example prompts **Clean Company Data** > Use People Data Labs to clean company data and walk me through the result in plain English. **Clean Company Post** > Use People Data Labs to clean company post and walk me through the result in plain English. **Clean Location Data** > Use People Data Labs to clean location data and walk me through the result in plain English. **Clean Location Post** > Use People Data Labs to clean location post and walk me through the result in plain English. ## 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 People Data Labs working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the People Data Labs API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected People Data Labs 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 People Data Labs. | 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 People Data Labs actions to the runtime in a format your agent can reliably use. | 23 tools for People Data Labs are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes People Data Labs 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 People Data Labs in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the People Data Labs 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 People Data Labs skill but can't call the tools The ClawHub skill teaches OpenClaw about People Data Labs, but the calls run through the ClawLink plugin and your connected account. Make sure People Data Labs 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 People Data Labs 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 People Data Labs tools People Data Labs 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 People Data Labs 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. ### People Data Labs 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 People Data Labs has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw People Data Labs integration? Yes. ClawLink is the fastest way to connect OpenClaw to People Data Labs: link your People Data Labs account once in the browser and OpenClaw can call the People Data Labs API through 23 ready-made tools — no custom code or token handling. ### How do I add People Data Labs to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink People Data Labs skill from ClawHub, then you click Connect in the dashboard to authorize People Data Labs. OpenClaw calls the tools from the next message — no config files, and the People Data Labs key you paste is stored server-side instead of in your environment. ### How long does it take to connect People Data Labs to OpenClaw? About two minutes. Sign in, click Connect next to People Data Labs in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring People Data Labs 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 People Data Labs working from chat. ### OpenClaw installed the People Data Labs skill but can't call the tools The ClawHub skill teaches OpenClaw about People Data Labs, but the calls run through the ClawLink plugin and your connected account. Make sure People Data Labs 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 - [Connect PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.