Apify
A RocketRide tool node for an agent that needs to run an Apify Actor or retrieve a dataset's items, with per-run item, time, and cost bounds.
About Apify
Apify is the external service this node accesses through its Python client. Its Actor runs can produce a default dataset, and this node can also read a dataset that already exists.
What it does
Use this node when an agent needs Actor-produced structured items or an existing Apify dataset. It exposes agent tools only—there are no pipeline lanes—and waits for an Actor run before reading its default dataset. Pick it over a general web or code-execution tool when the work is already packaged as an Apify Actor or dataset.
As a tool
The registered prefix is apify, so the agent sees apify.run_actor and apify.get_dataset_items.
| Function | Description |
|---|---|
apify.run_actor | Runs an Actor to completion, then reads items from its default dataset. |
apify.get_dataset_items | Reads items from an existing dataset. |
apify.run_actor
actor_id is required and may be an Actor ID or name. run_input is an optional object passed directly to that Actor, so its shape depends on the chosen Actor. limit is optional and is clamped to the configured item cap. The result contains success, dataset_id, count, and items; a run without a default dataset succeeds with an empty dataset ID and item list. Invalid input raises an error, and client errors from the Actor or dataset request are surfaced as tool failures.
apify.get_dataset_items
dataset_id is required; limit is optional and uses the same configured cap. The result contains success, count, and items. A missing dataset ID raises an error, and client request failures are surfaced rather than represented as an empty result.
Configuration
Set the API token first. The remaining settings are guardrails for agent-selected Actors; start with their defaults and increase them only when a known Actor needs more capacity.
Max Items
This is the upper bound for items returned by either tool and defaults to 100. A per-call limit can reduce the result set but can never exceed this value; invalid or omitted call limits use the cap. Raise it when the agent needs a larger complete result set, and keep it small when sending results into a limited agent context. Invalid or non-positive configuration falls back to 100.
Run Timeout (seconds)
This setting bounds both the Actor's run timeout and how long the client waits for it, defaulting to 120 seconds. Increase it for an Actor that legitimately takes longer to finish; leave it conservative for agent-chosen work so a stuck run cannot hold the pipeline indefinitely. Invalid or non-positive configuration falls back to 120.
Max Cost (USD)
This value is passed as the per-run total-charge limit for pay-per-event Actors and defaults to 1. Increase it only after establishing the expected cost of the specific Actor; the limit applies to run_actor, not dataset reads. A value that cannot be parsed as a decimal falls back to 1.
Authentication
Provide an Apify API token in API Token. The node creates its client at pipeline startup and fails to start when the configured token is empty.
Upstream docs
Schema
| Field | Type | Description | Default |
|---|---|---|---|
tool_apify.apikey | string | API Token Apify API token | "" |
tool_apify.max_cost_usd | number | Max Cost (USD) Spend limit per run for pay-per-event Actors. | 1 |
tool_apify.max_items | integer | Max Items Upper cap on items returned per call (agent requests are clamped to this). | 100 |
tool_apify.run_timeout_secs | integer | Run Timeout (seconds) Max seconds an Actor run may take before it is stopped. | 120 |
Dependencies
apify-client>=3,<4