Actions36
- Actors Actions
- Actor tasks Actions
- Datasets Actions
Overview
This node allows users to run an Apify actor task by specifying the task ID or a combination of the owner's username and task's name. It supports configuring runtime parameters such as timeout, memory limit, maximum number of items to return, specific actor build, and wait time for the task to finish. Additionally, users can specify webhooks for notifications and optionally provide a custom request body for the run. This node is useful for automating and managing actor task executions within workflows, enabling integration with Apify's platform for web scraping, automation, and data extraction tasks.
Use Case Examples
- Running a web scraping actor task with a specified timeout and memory limit to collect data from a website.
- Executing a pay-per-result actor task with a limit on the maximum number of items to control costs.
- Triggering an actor task and waiting for its completion to process the results immediately in the workflow.
Properties
| Name | Meaning |
|---|---|
| Actor Task ID | The ID of the actor task to run or a tilde-separated string combining the owner's username and the task's name. This identifies which actor task to execute. |
| Timeout | Optional timeout for the actor run in seconds, overriding the default task setting. |
| Memory | Memory limit for the actor run in megabytes, overriding the default task setting. |
| Max Items | Maximum number of items the actor run should return, useful for controlling pay-per-result costs. |
| Build | Specifies the actor build to run, either by build tag or build number, overriding the default task setting. |
| Wait For Finish | Maximum seconds to wait for the actor run to finish before returning, with a default of 0 (no wait) and a maximum of 60 seconds. |
| Webhooks | Base64-encoded JSON array defining optional webhooks for notifications on actor run events. |
| Use Custom Body | Flag to indicate whether to use a custom JSON body for the actor run request. |
| Custom Body | Custom JSON body to send with the actor run request if 'Use Custom Body' is enabled. |
Output
JSON
runId- The unique identifier of the actor run.status- The status of the actor run, e.g., RUNNING, SUCCEEDED, or FAILED.output- The output data or results produced by the actor run, if available.metadata- Additional metadata about the actor run, such as start time, end time, and resource usage.
Dependencies
- Apify API key credential
Troubleshooting
- Ensure the Actor Task ID is valid and correctly formatted; invalid IDs or URLs will cause errors.
- Timeout and memory values must be within allowed ranges; setting values too low or too high may cause the run to fail or be rejected.
- If using custom body, ensure the JSON is correctly formatted to avoid request errors.
- Webhooks must be Base64-encoded JSON arrays; incorrect encoding or format will prevent webhook notifications.
Links
- Apify Webhooks Documentation - Detailed information on setting up and using webhooks with Apify actor runs.
