How to connect Apify to OpenClaw
Connect Apify to OpenClaw with ClawLink: paste your Apify key once and 112 tools work from chat. No MCP server to run, nothing stored on your machine.
ApifyAPI KEYMCPRun web scrapers, manage Actors, datasets, and schedules. Once connected, OpenClaw can read and act on Apify from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Apify 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 Apify setup: install one ClawHub skill, connect Apify in the browser, and OpenClaw can call real Apify actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Apify skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Apify" (hith3sh/apify-actors) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/apify-actors
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Apify.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Apify
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Apify?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Apify in the ClawLink dashboard — paste your Apify API key once.
Verify the connection by asking OpenClaw:
Use Apify to actor task run sync get 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Apify is connected in the dashboard, that agent calls the same 112 Apify tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Apify MCP for OpenClaw
Looking for a Apify MCP server for OpenClaw? ClawLink connects Apify to OpenClaw and exposes 112 Apify tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Apify integration works the same way.
What the OpenClaw Apify integration can do
112 Apify tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 112.
30 of 112 Apify tools for OpenClaw
| Tool | What it does |
|---|---|
Actor task run sync get apify_actor_task_run_sync_get | Run a task synchronously and get results |
Acts get apify_acts_get | List all Actors |
Create task apify_create_task | Create a new Actor task |
Datasets get apify_datasets_get | List all datasets |
Get actor apify_get_actor | Get Actor details |
Get dataset items apify_get_dataset_items | Get items from a dataset |
Get key value record apify_get_key_value_record | Get a record from a key-value store |
Get list of runs apify_get_list_of_runs | List Actor runs |
Get list of tasks apify_get_list_of_tasks | List all tasks |
Get log apify_get_log | Get Actor run logs |
Key value stores get apify_key_value_stores_get | List all key-value stores |
Request queues get apify_request_queues_get | List all request queues |
Run actor apify_run_actor | Run an Actor asynchronously |
Run actor sync apify_run_actor_sync | Run an Actor synchronously and get results |
Run task apify_run_task | Run a task asynchronously |
Schedules get apify_schedules_get | List all schedules |
Users me get apify_users_me_get | Get current user account data |
Users me usage monthly get apify_users_me_usage_monthly_get | Get monthly usage summary |
Act runs last get apify_act_runs_last_get | Get the most recent run of a specific Actor |
Act version env var get apify_act_version_env_var_get | Get environment variable details for a specific Actor version |
Act version env vars get apify_act_version_env_vars_get | Get the list of environment variables for a specific Actor version |
Act version get apify_act_version_get | Get details about a specific version of an Actor |
Act versions get apify_act_versions_get | Get the list of versions of a specific Actor |
Act webhooks get apify_act_webhooks_get | Get a list of webhooks for a specific Actor |
Actor build get apify_actor_build_get | Get detailed information about a specific Actor build |
Actor build log get apify_actor_build_log_get | Retrieve the log file for a specific Actor build |
Actor builds get apify_actor_builds_get | Get a paginated list of all builds for a user |
Actor run get apify_actor_run_get | Get details about a specific Actor run |
Actor task get apify_actor_task_get | Get complete details about an Actor task |
Actor task run sync get dataset items get apify_actor_task_run_sync_get_dataset_items_get | Run an actor task synchronously and retrieve its dataset items |
Try it: find the Apify tool you need
Browse the 30 Apify tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Apify to actor task run sync get and walk me through the result in plain English.
Use Apify to acts get and walk me through the result in plain English.
Create it in Apify for me, then confirm the important fields before you finish.
Use Apify to datasets get 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 Apify working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Apify API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Apify 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 Apify. | 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 Apify actions to the runtime in a format your agent can reliably use. | 112 tools for Apify are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Apify 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 Apify in the browser, and the 112 tools above work from chat. There is no SDK and no config file, and the Apify key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Apify skill but can't call the tools
The ClawHub skill teaches OpenClaw about Apify, but the calls run through the ClawLink plugin and your connected account. Make sure Apify 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 Apify 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 Apify tools
Apify 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 Apify 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.
Apify 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 Apify has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Apify integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Apify: link your Apify account once in the browser and OpenClaw can call the Apify API through 112 ready-made tools — no custom code or token handling.
How do I add Apify to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Apify skill from ClawHub, then you click Connect in the dashboard to authorize Apify. OpenClaw calls the tools from the next message — no config files, and the Apify key you paste is stored server-side instead of in your environment.
How long does it take to connect Apify to OpenClaw?
About two minutes. Sign in, click Connect next to Apify in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Apify 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 Apify working from chat.
OpenClaw installed the Apify skill but can't call the tools
The ClawHub skill teaches OpenClaw about Apify, but the calls run through the ClawLink plugin and your connected account. Make sure Apify 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 tools
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
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.