Short answer: You can run apify actor in Apify by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Apify Run Apify Actor action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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" }] }" |
{"actorId": "apify/web-scraper","input": "{ \"startUrls\": [{ \"url\": \"https://example.com\" }] }"}
{"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.
Any of these apps can fire this action as part of a workflow.