# How to connect PredictLeads to OpenClaw (paste one key, 9 tools) > Connect PredictLeads to OpenClaw with ClawLink: paste your PredictLeads key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/predict-leads The usual route to PredictLeads 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 PredictLeads setup: install one ClawHub skill, connect PredictLeads in the browser, and OpenClaw can call real PredictLeads 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 PredictLeads. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PredictLeads** — 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 predict-leads # connect PredictLeads (browser OAuth) npx -y @useclawlink/cli actions predict-leads # list available actions npx -y @useclawlink/cli run predict-leads --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 PredictLeads in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PredictLeads API key once. Verify the connection by asking OpenClaw: > Use PredictLeads to discover companies 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 PredictLeads is connected in the dashboard, that agent calls the same 9 PredictLeads 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). ## PredictLeads MCP for OpenClaw Looking for a PredictLeads MCP server for OpenClaw? ClawLink connects PredictLeads to OpenClaw and exposes 9 PredictLeads 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 PredictLeads integration](https://claw-link.dev/hermes/predict-leads) works the same way. ## What the OpenClaw PredictLeads integration can do 9 PredictLeads tools are ready for OpenClaw once the account is connected. ### All 9 PredictLeads tools for OpenClaw | Tool | What it does | |---|---| | **Discover companies** `predict_leads_discover_companies` | Find companies using firmographic filters | | **Discover intelligence** `predict_leads_discover_intelligence` | Discover one page of jobs, technology adoption, news, financing, investor portfolio | | **Get API subscription** `predict_leads_get_api_subscription` | Check PredictLeads subscription status, monthly credit quota, and credits used | | **Get company** `predict_leads_get_company` | Retrieve one company by PredictLeads UUID or bare domain | | **Get company intelligence** `predict_leads_get_company_intelligence` | Retrieve one page of a company's jobs, technology detections, news, financing, SEC filings | | **Get intelligence record** `predict_leads_get_intelligence_record` | Retrieve one job opening, extended technology detection, technology, news event, SEC filing, or | | **Get similar companies** `predict_leads_get_similar_companies` | Find one page of companies similar to a specified PredictLeads company UUID or domain | | **List followed companies** `predict_leads_list_followed_companies` | List one page of companies already followed for PredictLeads webhook updates | | **Search technologies** `predict_leads_search_technologies` | Search PredictLeads' tracked technology catalog by fuzzy name | ## Example prompts **Discover Companies** > Use PredictLeads to discover companies and walk me through the result in plain English. **Discover Intelligence** > Use PredictLeads to discover intelligence and walk me through the result in plain English. **Get Api Subscription** > Pull the relevant data from PredictLeads, summarize it in plain English, and point out anything that needs attention. **Get Company** > Pull the relevant data from PredictLeads, 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 PredictLeads working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PredictLeads API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PredictLeads 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 PredictLeads. | 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 PredictLeads actions to the runtime in a format your agent can reliably use. | 9 tools for PredictLeads are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PredictLeads 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 PredictLeads in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the PredictLeads 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 PredictLeads skill but can't call the tools The ClawHub skill teaches OpenClaw about PredictLeads, but the calls run through the ClawLink plugin and your connected account. Make sure PredictLeads 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 PredictLeads 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 PredictLeads tools PredictLeads 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 PredictLeads 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. ### PredictLeads 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 PredictLeads has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw PredictLeads integration? Yes. ClawLink is the fastest way to connect OpenClaw to PredictLeads: link your PredictLeads account once in the browser and OpenClaw can call the PredictLeads API through 9 ready-made tools — no custom code or token handling. ### How do I add PredictLeads to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PredictLeads skill from ClawHub, then you click Connect in the dashboard to authorize PredictLeads. OpenClaw calls the tools from the next message — no config files, and the PredictLeads key you paste is stored server-side instead of in your environment. ### How long does it take to connect PredictLeads to OpenClaw? About two minutes. Sign in, click Connect next to PredictLeads in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PredictLeads 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 PredictLeads working from chat. ### OpenClaw installed the PredictLeads skill but can't call the tools The ClawHub skill teaches OpenClaw about PredictLeads, but the calls run through the ClawLink plugin and your connected account. Make sure PredictLeads 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 - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.