Run Apify Actor: Apify action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Actor ID actorId	string	Required	Actor ID. e.g. "apify/web-scraper"
Input input	json	Required	Input. (JSON object). e.g. "{ "startUrls": [{ "url": "https://example.com" }] }"

Sample request

{
  "actorId": "apify/web-scraper",
  "input": "{ \"startUrls\": [{ \"url\": \"https://example.com\" }] }"
}

Returns

{
  "data": {
    "id": "run123",
    "actId": "actor123",
    "status": "RUNNING",
    "startedAt": "2026-04-11T10:00:00Z",
    "defaultDatasetId": "dataset123"
  }
}

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

FAQ

Questions about Run Apify Actor.

What does the Run Apify Actor action do in Apify?

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.

What inputs does Run Apify Actor require?

Required: Actor ID, Input. 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 Run Apify Actor support batch operations?

Yes. Run Run Apify Actor inside a Loop node to process arrays. Tiny Command handles Apify's rate limits automatically so you don't have to throttle manually.

More actions