Apify

!Apify

Access Apify via the Apify API with managed API key authentication. Run Actors, manage tasks, inspect datasets and stores, and review logs or usage from chat.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Apify API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│    Apify API      │
│   (User Chat)   │     │   (API Key)  │     │   (Actors)       │
└─────────────────┘     └──────────────┘     └──────────────────┘
          │                       │                       │
          │  1. Install Plugin    │                       │
          │  2. Pair Device       │                       │
          │  3. Connect Apify      │                       │
          │                       │  4. Secure Proxy       │
          │                       │  5. API Requests        │
          │                       │                       │
          ▼                       ▼                       ▼
    ┌──────────┐           ┌──────────┐           ┌──────────┐
    │  SKILL   │           │ Dashboard│           │  Apify   │
    │  File    │           │ Auth     │           │ Console  │
    └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Apify again."

Quick Start

# List integrations
clawlink_list_integrations

# List Apify tools
clawlink_list_tools --integration apify

# Search for a specific tool
clawlink_search_tools --query "actor" --integration apify

Authentication

All Apify tool calls are authenticated automatically by ClawLink using the user's connected Apify API credentials.

No API key is required in chat. ClawLink stores the API key securely and injects it into every Apify API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=apify and connect Apify.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for apify in the list.

Verify Connection

clawlink_list_tools --integration apify

Response: Returns the live tool catalog for Apify.

Reconnect

If Apify tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=apify
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration apify

Discovery Workflow

1. Call clawlink_list_integrations to confirm Apify is connected.
2. Call clawlink_list_tools --integration apify to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration apify.
5. If no Apify tools appear, direct the user to https://claw-link.dev/dashboard?add=apify.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: List actors → Get dataset items → Return data   │
└─────────────────────────────────────────────────────────────┘
                               │
                               ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Describe tool → Preview changes → User approves   │
│           → Execute actor run                                │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer inspecting Actors, tasks, datasets, stores, queues, schedules, logs, and usage before launching new runs.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Tool Reference

Actors& Versions

Actor Runs

Tasks

Datasets

Key-Value Stores

Request Queues

Schedules

Code Examples

List Actors

clawlink_call_tool --tool "apify_acts_get" \
  --params '{
    "my": 1
  }'

Run an Actor synchronously

clawlink_call_tool --tool "apify_run_actor_sync" \
  --params '{
    "actor_id": "apify/web-scraper",
    "input": {
      "startUrls": [{"url": "https://example.com"}]
    }
  }'

Get dataset items

clawlink_call_tool --tool "apify_get_dataset_items" \
  --params '{
    "dataset_id": "YOUR_DATASET_ID",
    "limit": 100
  }'

Create a task

clawlink_call_tool --tool "apify_create_task" \
  --params '{
    "actor_id": "apify/web-scraper",
    "name": "My Scraper Task",
    "input": {
      "startUrls": [{"url": "https://example.com"}]
    }
  }'

Security & Permissions

• Access is scoped to the connected Apify account's data and Actor runs.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (deleting Actors, datasets, queues, schedules) are marked as high-impact and must be confirmed.
• Running Actors incurs compute costs; confirm before launching runs.
• Synchronous Actor runs timeout after 300 seconds; prefer async runs for large datasets.

Notes

• Actor IDs use the format username/actor-name or just actor-name for public Actors.
• For datasets larger than 1000 items, use pagination (offset/limit) to retrieve in batches.
• Logs are limited to the trailing 5 million characters.
• Synchronous runs are best for quick scrapes; longer jobs should use async runs.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly apify.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• Apify API Documentation
• Apify Platform
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=apify-actors
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo