Actor Run Search
Pricing
Pay per usage
Actor Run Search
Find historical Apify Actor runs by searching run inputs for exact or partial text matches. Quickly locate run IDs without manually browsing run history.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
TrueFalseMaybe
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
a day ago
Last modified
Categories
Share
Apify Run Input Search (Apify Actor)
This Apify Actor searches through an Actor’s historical run inputs and finds runs containing a specific keyword, phrase, URL, or partial text match.
The Actor scans all available runs, loads each run’s INPUT record from its Key-Value Store, and performs a case-insensitive text search against the full JSON input.
Results are exported into an Apify Dataset for easy filtering, analysis, or debugging.
How It Works
The Actor:
- Fetches all runs from a target Actor
- Extracts each run’s Key-Value Store ID
- Loads the
INPUTrecord from every run - Converts the input JSON into searchable text
- Searches for a user-provided term
- Stores matching runs in the Dataset
Use Cases
- Find runs containing a specific URL
- Locate runs by keyword or product name
- Search historical automation inputs
- Recover lost run configurations
- Audit old Actor runs
- Investigate customer executions
- Debug large-scale automation workflows
Input Options
actorId
The Actor ID whose runs should be searched.
- Type:
string - Required: yes
"actorId": "nwua9Gu5YrADL7ZDj"
searchTerm
Text to search for inside run inputs.
Supports:
- URLs
- partial strings
- keywords
- JSON fragments
- usernames
- arbitrary text
Search is:
-
case-insensitive
-
partial-match based
-
Type:
string -
Required: yes
"searchTerm": "kitchenaid"
"searchTerm": "https://www.ebay.com/usr/kitchenaid"
apiToken
Apify API token used to read the target Actor's runs and key-value stores.
- Type:
string - Required: yes
- Hidden securely in Actor input UI
"apiToken": "apify_api_xxxxxxxxx"
Security: use a limited-permission token
The Actor no longer falls back to its own run token — you must supply apiToken explicitly. This is intentional: the run's own token typically carries the full permissions of the account that started the run (read/write access to all Actors, runs, storages, etc.), while this Actor only ever performs read-only requests (listing runs, reading INPUT records). Requiring an explicit token forces a deliberate, scoped choice instead of silently inheriting full account access.
Recommended setup:
- In Apify Console, go to Settings → Integrations → API tokens and create a limited token.
- Scope it to read-only permissions on the specific Actor(s) whose runs you want to search (runs and key-value stores).
- Pass that limited token via the
apiTokeninput field.
This way, even if the token were leaked or the Actor misused, the blast radius is capped to read access on one Actor's run history rather than the whole account.
stopIfMatchFound
Controls whether the Actor stops after finding the first match.
true
- Stops early
- Faster execution
- Lower API usage
false
-
Processes all runs
-
Finds every possible match
-
Pushes all matches to dataset
-
Type:
boolean -
Default:
true
"stopIfMatchFound": false
concurrency
Number of runs processed simultaneously.
Higher values:
- increase speed
- increase API request volume
Recommended:
-
10-100for most cases -
100-500+for aggressive searching -
Type:
integer -
Default:
50
"concurrency": 100
Full Input Example
{"actorId": "nwua9Gu5YrADL7ZDj","searchTerm": "kitchenaid","apiToken": "apify_api_xxxxxxxxx","stopIfMatchFound": false,"concurrency": 100}
Output
Each dataset item represents one matching run input.
Output Fields
| Field | Type | Description |
|---|---|---|
runId | string | Apify Run ID |
storeId | string | Key-Value Store ID associated with the run |
matchedTerm | string | Search term used |
matched | boolean | Indicates successful match |
inputPreview | string | Truncated preview of input JSON |
input | object | Full original INPUT payload |
Output Example
{"runId": "3KH8s2a9LmP4xQvWc","storeId": "Jt9mKz1vQaY2LpNs","matchedTerm": "kitchenaid","matched": true,"inputPreview": "{\"startUrls\":[{\"url\":\"https://www.ebay.com/usr/kitchenaid\"}]}","input": {"startUrls": [{"url": "https://www.ebay.com/usr/kitchenaid"}]}}
Dataset Views
The Actor includes multiple Dataset views:
| View | Description |
|---|---|
Overview | General match overview |
Matches | Match-focused output |
Input Data | Full input payloads |
Store IDs | IDs only |
Notes
- The Actor searches only the
INPUTrecord of each run - Search uses
JSON.stringify(input).includes(...) - Matching is case-insensitive
- Extremely large Actors may take significant time to process
- Private Actors require a valid API token with access
- The Actor runs with 1024 MB of memory by default, matching its lightweight, read-only API usage
Legal Disclaimer
This Actor is not affiliated with or endorsed by Apify.
Users are responsible for:
- complying with Apify Terms of Service
- respecting account permissions
- ensuring authorized access to searched Actors