Actions11
- Actor Actions
- Actor Task Actions
- Actor Run Actions
- Dataset Actions
- Key-Value Store Actions
Overview
This node allows you to run an Actor on the Apify platform, which is a tool for web scraping, data extraction, and automation. Actors are reusable scripts or programs that perform specific tasks such as crawling websites, processing data, or automating workflows.
Common scenarios where this node is beneficial include:
- Running a web scraper Actor to collect data from a website.
- Triggering an automation Actor that processes input data and returns results.
- Executing custom data extraction or transformation logic hosted on Apify.
For example, you can use this node to start a crawler Actor with custom input parameters, wait for it to finish, and then use the extracted data in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Actor Source | Choose whether to select the Actor from your recently used Actors or browse the Apify Store. Options: "Recently Used Actors", "Apify Store Actors". |
| Actor | The Actor to run. You can select it from a list of available Actors, specify by URL, or provide the Actor ID directly. |
| Input JSON | JSON input for the Actor run. This defines the configuration or parameters passed to the Actor when it starts. If empty, the Actor uses its default input configuration. |
| Wait for Finish | Boolean flag indicating whether the node should wait for the Actor run to complete before continuing. If true, the node waits until the run finishes (successfully or not). |
| Timeout | Optional timeout in seconds for the Actor run. Overrides the default timeout configured for the Actor if specified. |
| Memory | Memory limit for the Actor run in megabytes. You can choose from predefined options ranging from 128 MB up to 32 GB. Defaults to 1024 MB (1 GB) if not specified. |
| Build Tag | Specifies the build tag of the Actor to run. By default, the latest build is used unless another tag is provided. |
| Authentication | Selects the authentication method to use for connecting to Apify. Options are API Key or OAuth2. |
Output
The node outputs the result of the Actor run in the json field of the output data. This typically includes details about the run such as run ID, status, output data produced by the Actor, and metadata related to the execution.
If the Actor produces binary data, it will be included in the binary output fields accordingly, allowing further processing or saving within the workflow.
Dependencies
- Requires an active connection to the Apify platform via either an API key or OAuth2 authentication.
- The user must have access rights to run the selected Actor on Apify.
- Proper configuration of authentication credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid Actor ID or URL: Ensure the Actor identifier is correct and accessible.
- Authentication failures: Verify that the API key or OAuth2 token is valid and has sufficient permissions.
- Timeout errors: If the Actor takes longer than the specified timeout, the node may error out. Adjust the timeout property or workflow timeout settings accordingly.
- Memory limits exceeded: If the Actor requires more memory than allocated, increase the memory setting.
Error messages:
- "Not a valid Actor URL": Occurs if the provided URL does not match the expected pattern. Use a correct Apify Actor URL.
- "Not a valid Actor ID": Happens when the Actor ID format is incorrect. Provide a valid alphanumeric ID.
- Authentication errors: Check credentials and reauthenticate if needed.