Actions11
- Actor Actions
- Actor Task Actions
- Actor Run Actions
- Dataset Actions
- Key-Value Store Actions
Overview
This node integrates with the Apify platform, specifically to retrieve details about a single Actor Run. An Actor Run represents an execution instance of an Apify Actor, which is a serverless program designed for web scraping, automation, or data extraction tasks.
The "Get run" operation under the "Actor Run" resource fetches detailed information about a specific run by its unique identifier. This is useful when you want to monitor, analyze, or process the results and metadata of a particular Actor execution.
Practical examples:
- Fetching the status and output of a previously started web scraping job.
- Retrieving logs or metadata from a specific run to debug or audit the execution.
- Integrating Apify run data into workflows for further processing or reporting.
Properties
| Name | Meaning |
|---|---|
| Run ID | The unique identifier of the Actor Run to retrieve. You can specify it in three ways: • From list: Select from a list of recent runs. • By URL: Provide the full Apify Actor Run URL (e.g., https://console.apify.com/actors/runs/{runId}#output).• ID: Enter the raw run ID string directly. |
| Authentication | Choose the authentication method to access the Apify API: • API Key • OAuth2 |
Output
The node outputs JSON data representing the detailed information of the specified Actor Run. This typically includes:
- Run metadata such as run ID, status, start and finish times.
- Input parameters used for the run.
- Results or output dataset references.
- Logs or error messages if available.
- Other relevant execution details provided by the Apify API.
If the run produced binary data (e.g., files), this would be referenced or accessible via URLs in the JSON output rather than embedded directly.
Dependencies
- Requires an active connection to the Apify platform.
- Needs either an API key credential or OAuth2 authentication configured in n8n to authorize requests.
- Network access to Apify's API endpoints.
Troubleshooting
- Invalid Run ID or URL: If the Run ID is malformed or the URL does not match the expected pattern, the node will reject the input. Ensure the Run ID matches the alphanumeric format and URLs follow the Apify console structure.
- Authentication errors: Using incorrect or expired API keys or OAuth tokens will cause authorization failures. Verify credentials are valid and have sufficient permissions.
- Run not found: If the specified run ID does not exist or belongs to another user/account, the API will return an error. Confirm the run ID is correct and accessible.
- Network issues: Connectivity problems to Apify servers will result in request timeouts or failures. Check network settings and firewall rules.