Start free
ActionApifyUpdated June 2026

How do I check the status of an Apify actor run?

Short answer: You can get actor run status in Apify by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Apify Get Actor Run Status action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 4 Apify actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Run ID
run_id
stringRequiredRun ID (required)
Sample request
{
  "run_id": "{{trigger.run_id}}"
}
Returns
{
  "data": {
    "id": "run-abc",
    "status": "SUCCEEDED",
    "defaultDatasetId": "ds-xyz"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Actor Run Status.

Any of these apps can fire this action as part of a workflow.

Gmail → Apify
1 Gmail triggers
Slack → Apify
13 Slack triggers
Google Sheets → Apify
2 Google Sheets triggers
HubSpot → Apify
18 HubSpot triggers
FAQ

Questions about Get Actor Run Status.

What does the Get Actor Run Status action do in Apify?
Returns the current state of a run — RUNNING, SUCCEEDED, FAILED, or ABORTED — plus runtime stats and compute usage. Poll for completion in workflows that need to wait, or pair with the actor's webhook for push-based notification.
What inputs does Get Actor Run Status require?
Required: Run ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Apify returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get Actor Run Status support batch operations?
Yes. Run Get Actor Run Status inside a Loop node to process arrays. TinyCommand handles Apify's rate limits automatically so you don't have to throttle manually.
More actions

Other Apify actions.

Action
Get Dataset Items
Returns the records the actor wrote to its dataset (typically one record per scraped item — product, profile, search result). Shape depends entirely on the actor; check the actor's README in Apify Store for the schema before parsing downstream.
Action
List Actors
Returns every actor in the account — custom-built actors plus Apify Store actors the account has installed. Useful for inventorying available scrapers at workflow-setup time.
Action
Run Apify Actor
Starts an actor with the configured input parameters. Returns the run ID immediately; the actor processes async. For long scrapes, configure the actor's webhook to POST completion to a Tiny Command trigger URL instead of polling.