Apify Action Block
What it does: Runs Apify actors and saved tasks (web scrapers, crawlers, data extractors) and pulls their results into your workflow.
🕷️
In simple terms: Point the block at any actor from the Apify Store (Google Maps scraper, website content crawler, Instagram scraper…), give it an input, and get back structured JSON you can feed into an LLM, a database, or a Google Sheet.
Credentials
Create an API token in Apify Console → Settings → API & Integrations and paste it when connecting the block.
Actions
| Action | What it does | Output |
|---|---|---|
| Run Actor | Starts an actor run, optionally waits up to 60 s | Run object (id, status, defaultDatasetId, defaultKeyValueStoreId) |
| Run Actor & Get Results | Runs the actor synchronously and returns its dataset items in one step (best for runs under ~5 min) | Array of items |
| Run Task | Runs a saved task (actor + stored input), optional input overrides | Run object |
| Get Run | Fetches run status; can wait up to 60 s for it to finish | Run object |
| Abort Run | Aborts a running actor | Run object |
| Get Dataset Items | Reads items from a dataset id or a run id | Array of items |
| Get Last Run Dataset | Items from the actor's most recent run (optionally filtered by status) | Array of items |
| Get Key-Value Record | Reads a record (default OUTPUT) from a store or run | Record value |
| List Actors / Get Actor / List Runs | Discovery helpers | Apify list / actor / runs objects |
Tips
- Actor IDs use
username~actor-name(e.g.apify~website-content-crawler). A/is converted automatically. - Input is the same JSON you see on the actor's Input tab in the Console.
- For long-running actors use Run Actor, then a Wait block, then Get Dataset Items with
{{apify.defaultDatasetId}}. - Use
fields+clean=trueon dataset reads to keep only the columns you need.