# How to connect Scrape Do to OpenClaw (paste one key, 16 tools) > Connect Scrape Do to OpenClaw with ClawLink: paste your Scrape Do key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/scrape-do The usual route to Scrape Do 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 Scrape Do setup: install one ClawHub skill, connect Scrape Do in the browser, and OpenClaw can call real Scrape Do 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 Scrape Do. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Scrape Do** — 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 scrape-do # connect Scrape Do (browser OAuth) npx -y @useclawlink/cli actions scrape-do # list available actions npx -y @useclawlink/cli run scrape-do --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 Scrape Do in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Scrape Do API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Scrape Do, 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 Scrape Do is connected in the dashboard, that agent calls the same 16 Scrape Do 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). ## Scrape Do MCP for OpenClaw Looking for a Scrape Do MCP server for OpenClaw? ClawLink connects Scrape Do to OpenClaw and exposes 16 Scrape Do 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 Scrape Do integration](https://claw-link.dev/hermes/scrape-do) works the same way. ## What the OpenClaw Scrape Do integration can do 16 Scrape Do tools are ready for OpenClaw once the account is connected. ### All 16 Scrape Do tools for OpenClaw | Tool | What it does | |---|---| | **Get account info** `scrape_do_get_account_info` | Retrieves account information and usage statistics from Scrape.do | | **Get amazon offers** `scrape_do_get_amazon_offers` | Get all seller offers for any Amazon product | | **Get amazon product** `scrape_do_get_amazon_product` | Extract structured product data from Amazon product detail pages (PDP) | | **Get amazon raw HTML** `scrape_do_get_amazon_raw_html` | Get raw HTML from any Amazon page with ZIP code geo-targeting | | **Get async account info** `scrape_do_get_async_account_info` | Get account information for the Async API including concurrency limits and usage statistics | | **Get async job** `scrape_do_get_async_job` | Retrieve details and status of a specific asynchronous scraping job | | **Get async task** `scrape_do_get_async_task` | Retrieve the result of a specific task within an asynchronous job | | **Get page** `scrape_do_get_page` | A tool to scrape web pages using scrape.do's API service | | **List async jobs** `scrape_do_list_async_jobs` | List all asynchronous scraping jobs | | **Proxy mode** `scrape_do_proxy_mode` | Implements the Proxy Mode functionality of scrape.do, which allows routing requests through | | **Scrape URL post** `scrape_do_scrape_url_post` | Scrape web pages using POST method via scrape.do API | | **Search amazon** `scrape_do_search_amazon` | Search Amazon and scrape product listings with structured results | | **Set regional geo code** `scrape_do_set_regional_geo_code` | Allows users to set a broader geographical targeting by specifying a region code instead of a | | **Create async job** `scrape_do_create_async_job` | Create an asynchronous scraping job with specified targets and options | | **Set block URLS** `scrape_do_set_block_urls` | Allows users to block specific URLs during the scraping process | | **Cancel async job** `scrape_do_cancel_async_job` | Cancel an asynchronous scraping job | ## Example prompts **Get Account Info** > Pull the relevant data from Scrape Do, summarize it in plain English, and point out anything that needs attention. **Get Amazon Offers** > Pull the relevant data from Scrape Do, summarize it in plain English, and point out anything that needs attention. **Get Amazon Product** > Pull the relevant data from Scrape Do, summarize it in plain English, and point out anything that needs attention. **Get Amazon Raw Html** > Pull the relevant data from Scrape Do, 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 Scrape Do working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Scrape Do API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Scrape Do 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 Scrape Do. | 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 Scrape Do actions to the runtime in a format your agent can reliably use. | 16 tools for Scrape Do are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Scrape Do 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 Scrape Do in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Scrape Do 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 Scrape Do skill but can't call the tools The ClawHub skill teaches OpenClaw about Scrape Do, but the calls run through the ClawLink plugin and your connected account. Make sure Scrape Do 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 Scrape Do 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 Scrape Do tools Scrape Do 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 Scrape Do 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. ### Scrape Do 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 Scrape Do has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Scrape Do integration? Yes. ClawLink is the fastest way to connect OpenClaw to Scrape Do: link your Scrape Do account once in the browser and OpenClaw can call the Scrape Do API through 16 ready-made tools — no custom code or token handling. ### How do I add Scrape Do to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Scrape Do skill from ClawHub, then you click Connect in the dashboard to authorize Scrape Do. OpenClaw calls the tools from the next message — no config files, and the Scrape Do key you paste is stored server-side instead of in your environment. ### How long does it take to connect Scrape Do to OpenClaw? About two minutes. Sign in, click Connect next to Scrape Do in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Scrape Do 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 Scrape Do working from chat. ### OpenClaw installed the Scrape Do skill but can't call the tools The ClawHub skill teaches OpenClaw about Scrape Do, but the calls run through the ClawLink plugin and your connected account. Make sure Scrape Do 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 DataRobot](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 tools](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. - [Connect 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.