Actions11
- Actor Actions
- Actor Task Actions
- Actor Run Actions
- Dataset Actions
- Key-Value Store Actions
Overview
This node allows you to run an Actor Task on the Apify platform, which is a service for web scraping, automation, and data extraction. The node triggers a specific pre-configured task (an "Actor Task") that runs an automated job such as crawling websites, processing data, or interacting with APIs.
Common scenarios include:
- Running scheduled or on-demand web scrapers.
- Triggering data extraction workflows.
- Automating repetitive web tasks like form submissions or data collection.
- Integrating Apify tasks into larger n8n workflows for further processing or notifications.
For example, you might use this node to start a web scraper that collects product prices from an e-commerce site and then pass the results downstream in your workflow for analysis or storage.
Properties
| Name | Meaning |
|---|---|
| Actor Task | Select the Actor Task to run. You can choose it from a list, provide its URL, or specify its ID directly. |
| Use Custom Body | Whether to send a custom JSON input body to the task instead of the default input. |
| Input (JSON) | The custom JSON input to send to the Actor Task if "Use Custom Body" is enabled. |
| Wait for Finish | If true, the node waits until the Actor Task run finishes (successfully or not) before continuing the workflow. |
| Timeout | Optional timeout in seconds for the Actor Task run. Overrides the task's default timeout if set. |
| Memory | Memory limit for the Actor Task run. Options range from 128 MB up to 32 GB. Defaults to 1024 MB (1 GB). |
| Build | Specify a particular build tag or build number of the Actor to run. Defaults to the build configured in the task settings (usually the latest). |
| Authentication | Choose the authentication method to connect to Apify: either an API key credential or OAuth2. |
Output
The node outputs JSON data representing the result of the Actor Task run. This typically includes details about the run such as status, output dataset, logs, and metadata returned by Apify after execution.
If "Wait for Finish" is enabled, the output corresponds to the completed run's data. Otherwise, it may contain information about the started run without waiting for completion.
The node does not output binary data.
Dependencies
- Requires an Apify account and an API key or OAuth2 credentials configured in n8n.
- Needs network access to Apify's API endpoints.
- The node depends on Apify's platform services to execute Actor Tasks.
Troubleshooting
- Invalid Actor Task ID or URL: Ensure the Actor Task identifier is correct and matches the expected format. The node validates URLs and IDs with regex; incorrect formats will cause errors.
- Authentication errors: Verify that the API key or OAuth2 credentials are valid and have sufficient permissions.
- Timeouts: If the task takes longer than the specified timeout or the workflow timeout, the node may error out. Adjust timeouts accordingly.
- Memory limits: Setting memory too low may cause the task to fail; set appropriate memory based on task requirements.
- Waiting for finish: If "Wait for Finish" is enabled but the task never completes, the workflow may hang or timeout. Consider disabling wait or increasing workflow timeout.