# How to connect Getprospect to OpenClaw (paste one key, 22 tools) > Connect Getprospect to OpenClaw with ClawLink: paste your Getprospect key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/getprospect The usual route to Getprospect 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 Getprospect setup: install one ClawHub skill, connect Getprospect in the browser, and OpenClaw can call real Getprospect 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 Getprospect. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Getprospect** — 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 getprospect # connect Getprospect (browser OAuth) npx -y @useclawlink/cli actions getprospect # list available actions npx -y @useclawlink/cli run getprospect --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 Getprospect in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Getprospect API key once. Verify the connection by asking OpenClaw: > Create it in Getprospect for me, then confirm the important fields before you finish. ### 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 Getprospect is connected in the dashboard, that agent calls the same 22 Getprospect 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). ## Getprospect MCP for OpenClaw Looking for a Getprospect MCP server for OpenClaw? ClawLink connects Getprospect to OpenClaw and exposes 22 Getprospect 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 Getprospect integration](https://claw-link.dev/hermes/getprospect) works the same way. ## What the OpenClaw Getprospect integration can do 22 Getprospect tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 22. ### 19 of 22 Getprospect tools for OpenClaw | Tool | What it does | |---|---| | **Create export** `getprospect_create_export` | Create a new export job | | **Get account workspace limits** `getprospect_get_account_workspace_limits` | Retrieve workspace limits for the user's account | | **Get all companies** `getprospect_get_all_companies` | Retrieve all companies | | **Get all lists** `getprospect_get_all_lists` | Retrieve all prospect contact lists | | **Get single company** `getprospect_get_single_company` | Retrieve details of a single company by its ID | | **Get single contact** `getprospect_get_single_contact` | Retrieve details of a single contact | | **Search companies** `getprospect_search_companies` | Search for companies by name | | **Search contacts** `getprospect_search_contacts` | Search for contacts by filters | | **Search contacts related to list** `getprospect_search_contacts_related_to_list` | Search contacts in a specific list | | **Search through lists by name** `getprospect_search_through_lists_by_name` | Search contact lists by name | | **Verify email address** `getprospect_verify_email_address` | Verify an email's deliverability | | **Apply coupon code** `getprospect_apply_coupon_code` | Apply a coupon code to the user's account | | **Create company** `getprospect_create_company` | Create a new company | | **Create contact** `getprospect_create_contact` | Create a new contact | | **Create list** `getprospect_create_list` | Create a new contact list | | **Post add contacts to list** `getprospect_post_add_contacts_to_list` | Add contacts to a specified list | | **Update company** `getprospect_update_company` | Update details of an existing company | | **Update contact** `getprospect_update_contact` | Update details of an existing contact | | **Update list** `getprospect_update_list` | Update a contact list's name | ## Example prompts **Create Export** > Create it in Getprospect for me, then confirm the important fields before you finish. **Get Account Workspace Limits** > Pull the relevant data from Getprospect, summarize it in plain English, and point out anything that needs attention. **Get All Companies** > Pull the relevant data from Getprospect, summarize it in plain English, and point out anything that needs attention. **Get All Lists** > Pull the relevant data from Getprospect, 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 Getprospect working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Getprospect API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Getprospect 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 Getprospect. | 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 Getprospect actions to the runtime in a format your agent can reliably use. | 22 tools for Getprospect are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Getprospect 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 Getprospect in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Getprospect 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 Getprospect skill but can't call the tools The ClawHub skill teaches OpenClaw about Getprospect, but the calls run through the ClawLink plugin and your connected account. Make sure Getprospect 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 Getprospect 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 Getprospect tools Getprospect 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 Getprospect 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. ### Getprospect 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 Getprospect has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Getprospect integration? Yes. ClawLink is the fastest way to connect OpenClaw to Getprospect: link your Getprospect account once in the browser and OpenClaw can call the Getprospect API through 22 ready-made tools — no custom code or token handling. ### How do I add Getprospect to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Getprospect skill from ClawHub, then you click Connect in the dashboard to authorize Getprospect. OpenClaw calls the tools from the next message — no config files, and the Getprospect key you paste is stored server-side instead of in your environment. ### How long does it take to connect Getprospect to OpenClaw? About two minutes. Sign in, click Connect next to Getprospect in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Getprospect 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 Getprospect working from chat. ### OpenClaw installed the Getprospect skill but can't call the tools The ClawHub skill teaches OpenClaw about Getprospect, but the calls run through the ClawLink plugin and your connected account. Make sure Getprospect 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 ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences