/apify

name: apify
description: |
  Apify integration. Manage Actors, Datasets, KeyValueStores, RequestQueues, Tasks. Use when the user wants to interact with Apify data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

Apify

Apify is a web scraping and automation platform. It allows developers and businesses to extract data from websites, automate workflows, and build web robots. It's used by data scientists, marketers, and researchers for tasks like lead generation, market research, and content monitoring.

Official docs: https://docs.apify.com/

Apify Overview

• **Actor**
• **Run**
• **Task**
• **Run**
• **Webhook**
• **Dataset**
• **Record**
• **KeyValueStore**
• **Record**
• **RequestQueue**
• **Request**

Use action names and parameters as needed.

Working with Apify

This skill uses the Membrane CLI to interact with Apify. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Apify

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://apify.com" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | | --- | --- | --- | | Search Actors in Store | search-actors-in-store | Search for Actors in the Apify Store | | Get Key-Value Store | get-key-value-store | Get details of a specific key-value store by ID | | Get Log | get-log | Get log for an Actor build or run | | Get Key-Value Store Record | get-key-value-store-record | Get a record from a key-value store | | Get Current User | get-current-user | Get private data of the currently authenticated user | | Get Monthly Usage | get-monthly-usage | Get monthly usage statistics for the current user | | List Key-Value Stores | list-key-value-stores | Get list of key-value stores | | Run Task | run-task | Run an Actor task and immediately return without waiting for the run to finish | | Get Task | get-task | Get details of a specific Actor task by ID | | Get Dataset Items | get-dataset-items | Get items from a dataset | | List Tasks | list-tasks | Get list of Actor tasks | | Get Dataset | get-dataset | Get details of a specific dataset by ID | | List Datasets | list-datasets | Get list of datasets | | Get Run | get-run | Get details of a specific Actor run by ID | | Run Actor | run-actor | Run an Actor and immediately return without waiting for the run to finish | | Get Actor | get-actor | Get details of a specific Actor by ID or name | | List Runs | list-runs | Get list of Actor runs for the user | | Abort Run | abort-run | Abort an Actor run | | List Actors | list-actors | Get list of Actors owned by the user |

Running actions

membrane act