APIFY n8n INTEGRATION: AUTOMATE APIFY WITH N8N

The Scrape single URL action is perfect for quick, targeted scraping tasks where you need to extract data from one specific webpage. This action leverages Apify's powerful crawling infrastructure directly from your n8n workflow.

Key parameters: You must provide your Apify API key connection through a dropdown selection, set the Resource to "Actor," and specify the Operation as "Scrape Single URL." The URL parameter requires a valid webpage address in text format, and you must select a Crawler Type from the dropdown menu to define the crawling method.

Use cases: Extract product details from a single e-commerce page, scrape a specific article for content analysis, or pull structured data from any publicly accessible URL as part of a larger workflow.

Run an Actor gives you full control to execute any Apify actor directly from n8n, passing custom inputs and configuring execution parameters. This is your workhorse action for triggering scraping jobs programmatically.

Key parameters: Authentication requires your Apify API key connection. You select an Actor Source (like "Recently Used Actors") and specify the exact Actor to execute. Optional parameters include Input JSON for custom runtime data, a Wait for Finish toggle (defaults to false), Timeout in milliseconds, Memory allocation (e.g., "1024 MB"), and Build Tag to target specific actor versions.

Use cases: Launch scheduled scraping jobs from n8n triggers, dynamically pass search parameters based on upstream workflow data, or run different actor configurations based on conditional logic in your automation.

This action combines actor execution with automatic dataset retrieval—run your scraper and get results back in one step. Perfect for workflows that need to immediately process scraped data.

Key parameters: Required parameters include your Apify API key connection, Actor Source selection, and Actor identification (can be by ID). Optional configurations allow Input JSON for custom parameters, Timeout in seconds, Memory allocation in megabytes, and Build Tag for version targeting.

Use cases: Scrape and immediately enrich CRM contacts, extract data and send directly to Google Sheets, or build pipelines where scraped output feeds directly into downstream processing nodes.

Retrieve a comprehensive list of all your actor runs, with filtering and pagination options. Essential for monitoring, auditing, and building dashboards around your scraping operations.

Key parameters: Requires Apify API key connection and Resource set to "Actor Run." Optional parameters include Offset (starting point for pagination, defaults to 0), Limit (maximum results, defaults to 50), Desc toggle for including description data, and Status dropdown to filter by execution status like "SUCCEEDED."

Use cases: Build monitoring dashboards showing recent scraping activity, audit successful vs. failed runs over time, or create alerts when failure rates exceed thresholds.

Execute a pre-configured actor task and retrieve its dataset in one seamless operation. Tasks are saved actor configurations in Apify, making this action ideal for standardized, repeatable scraping jobs.

Key parameters: Authentication via Apify API key connection is required, with Resource set to "Actor Task." You must select the specific Actor Task to run (by ID or selection). Optional parameters include Use Custom Body toggle, Timeout for maximum execution time, required Memory allocation dropdown, and optional Build specification for actor version control.

Use cases: Run standardized scraping jobs with consistent configurations, execute recurring data extraction tasks, or trigger pre-built tasks from external events.

Retrieve detailed information about runs for a specific actor. Use this to monitor individual actor performance or fetch run history for reporting.

Key parameters: Requires Apify API key connection and Resource set to "Actor Run." You must specify which Actor's runs to retrieve (by ID or selection). Optional parameters include Offset for pagination (defaults to 0), Limit for maximum results (defaults to 50), Desc toggle for descending sort order, and Status dropdown for filtering by run status.

Use cases: Generate actor-specific performance reports, track run history for compliance purposes, or identify patterns in execution times and outcomes.

Execute a saved actor task with full parameter control. Unlike "Run Task and Get Dataset," this action doesn't automatically retrieve results—giving you more flexibility in complex workflows.

Key parameters: Required dropdown for Apify API key connection, Resource set to "Actor Task," and Actor Task specification (by ID). Optional parameters include Use Custom Body toggle, Wait for Finish toggle (defaults off), Timeout in milliseconds, required Memory allocation like "1024 MB (1 GB)," and optional Build number for specific actor versions.

Use cases: Trigger tasks asynchronously without waiting for results, run tasks where dataset retrieval happens later via separate action, or build fire-and-forget scraping workflows.

Retrieve detailed information about a single, specific actor run using its unique Run ID. Perfect for checking status, debugging, or pulling metadata about completed runs.

Key parameters: Requires Apify API key connection for API access and Resource set to "Actor Run." The critical parameter is Run ID—a required text input that accepts expressions to identify the specific run you want to retrieve information about.

Use cases: Check status of a previously triggered run, retrieve execution logs for debugging failed jobs, or pull run metadata for reporting and analytics.

Quickly access the most recent run of a specific actor, optionally filtered by status. This shortcut saves you from querying run lists when you just need the latest execution.

Key parameters: Required dropdown for Apify API key connection and Resource set to "Actor." You must specify the Actor to query (by ID or expression). Optional Status dropdown allows filtering by execution status like "SUCCEEDED."

Use cases: Get the latest successful scrape results, check if the most recent run completed without errors, or build workflows that always reference fresh data from the last execution.

Retrieve items from a specific Apify dataset. After running an actor, use this action to fetch the extracted data for processing in your workflow.

Key parameters: Required authentication via Apify API key connection, with Resource fixed to "Dataset" and Operation set to "Get Items." You must provide a Dataset ID (unique identifier as text input), with optional Offset for pagination starting point and required Limit for number of items to retrieve (defaults to 50).

Use cases: Fetch scraped data for transformation or enrichment, pull dataset contents into other applications like databases or spreadsheets, or paginate through large datasets in chunks.

Access specific records from Apify's key-value stores using their unique keys. Key-value stores are perfect for caching, configuration storage, or passing data between actors.

Key parameters: Required dropdown for Apify API key connection, with Resource fixed to "Key-Value Store." You must provide a Key-Value Store ID (required, by ID) and a Key-Value Store Record Key (required text input) to retrieve the specific record.

Use cases: Fetch cached scraping results, retrieve configuration data stored in Apify, or access screenshots, PDFs, or other files stored in key-value stores.