AutoGineer
Generated banner for Apify Ultimate Scraper
Generated logo for Apify Ultimate Scraper

Apify Ultimate Scraper

ApifyOfficialPublished by Apify

  • Skill
  • Tool integration
  • Automation and integrations
  • Apache-2.0
  • Low risk
Download ZIP

From the author

Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, LinkedIn, X/Twitter, Google Maps, Google Search, Google Trends, Reddit, Airbnb, Yelp, and 15+ more platforms. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research, content analytics, audience analysis, review analysis, SEO intelligence, recruitment, or any data extraction task.
— the description by Apify

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The apify-ultimate-scraper skill provides a structured, AI-assisted approach to web data extraction. It leverages the Apify CLI to interact with a wide range of platform-specific Actors, ensuring consistent telemetry, machine-readable output, and cost-conscious execution. The skill includes a comprehensive index for selecting the right tool for tasks ranging from social media analytics to e-commerce price monitoring, while enforcing safety protocols for cost estimation and error handling.

What it does

  • Provides a standardized CLI workflow for searching, configuring, and running web scrapers.
  • Ensures machine-readable output by enforcing JSON formatting and stderr redirection.
  • Includes a cost estimation protocol for pay-per-event (PPE) Actors to prevent unexpected billing.
  • Facilitates dynamic retrieval of Actor input schemas and documentation.
  • Supports both synchronous execution for quick lookups and asynchronous polling for large-scale scrapes.
  • Integrates with a library of workflow guides for specific use cases like lead generation and SEO.

When to use it

  • When you need to extract structured data from social media, e-commerce, or search engine platforms.
  • When performing competitive intelligence, brand monitoring, or market research.
  • When you require a repeatable, automated pipeline for data collection.
  • When you need to verify the cost implications of a scraping task before execution.

Advantages

  • Reduces manual configuration errors through standardized CLI usage patterns.
  • Prevents budget overruns with built-in cost estimation and warning thresholds.
  • Provides a unified interface for interacting with over 100 different scraping tools.
  • Ensures stable, parseable output for downstream data processing.

Usage examples

“Find a scraper for Instagram follower counts.”
The agent searches the Actor index, identifies 'apify/instagram-followers-count-scraper', and provides the command to fetch its input schema.
“Scrape the top 50 results for 'AI tools' on Google Search.”
The agent selects the appropriate Google Search Actor, estimates the cost if applicable, runs the scrape, and presents the results as a formatted JSON list.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/apify/apify-ultimate-scraper/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip apify-ultimate-scraper.zip -d .agents/skills

Documentation by Apify

Universal web scraper

AI-driven data extraction from ~100 Actors across 15+ platforms via the Apify CLI.

Rules for every apify command:

  1. Pass --json for machine-readable output (stable across CLI versions).

  2. Pass --user-agent apify-agent-skills/apify-ultimate-scraper for telemetry attribution.

  3. Redirect stderr with 2>/dev/null (stderr contains progress messages that break JSON parsers).

Prerequisites

  • Apify CLI v1.5.0+ (npm install -g apify-cli)

  • Authenticated session (see below)

Authentication

If a CLI command fails with an auth error, authenticate using one of these methods:

  1. OAuth (interactive): apify login (opens browser)

  2. Environment variable: export APIFY_TOKEN=your_token_here

  3. From .env file: source .env (if the file contains APIFY_TOKEN=...)

Generate token: https://console.apify.com/settings/integrations

Workflow

Step 1: Understand goal and select Actor

Identify the target platform and use case. Read references/actor-index.md to find the right Actor.

If the task involves a multi-step pipeline, also read the matching workflow guide:

Task involves...Read
leads, contacts, emails, B2Breferences/workflows/lead-generation.md
competitor, ads, pricingreferences/workflows/competitive-intel.md
influencer, creatorreferences/workflows/influencer-vetting.md
brand, mentions, sentimentreferences/workflows/brand-monitoring.md
reviews, ratings, reputationreferences/workflows/review-analysis.md
SEO, SERP, crawl, content, RAGreferences/workflows/content-and-seo.md
analytics, engagement, performancereferences/workflows/social-media-analytics.md
trends, keywords, hashtagsreferences/workflows/trend-research.md
jobs, recruiting, candidatesreferences/workflows/job-market-and-recruitment.md
real estate, listings, hotelsreferences/workflows/real-estate-and-hospitality.md
price monitoring, e-commerce, productsreferences/workflows/ecommerce-price-monitoring.md
contact enrichment, email extractionreferences/workflows/contact-enrichment.md
knowledge base, RAG, LLM data feedreferences/workflows/knowledge-base-and-rag.md
company research, due diligencereferences/workflows/company-research.md

If no Actor matches in the index, search dynamically:

apify actors search "KEYWORDS" --user-agent apify-agent-skills/apify-ultimate-scraper --json --limit 10 2>/dev/null

From results: items[].username/items[].name (Actor ID), items[].title, items[].stats.totalUsers30Days, items[].currentPricingInfo.pricingModel.

Step 2: Fetch Actor schema and check gotchas

Fetch the input schema dynamically:

apify actors info "ACTOR_ID" --user-agent apify-agent-skills/apify-ultimate-scraper --input --json 2>/dev/null

Also read references/gotchas.md to check for common pitfalls for the selected Actor.

For Actor documentation: apify actors info "ACTOR_ID" --user-agent apify-agent-skills/apify-ultimate-scraper --readme

Step 3: Configure and run

Skip user preferences for simple lookups (e.g., "Nike's follower count"). Go straight to running with quick answer mode.

For larger tasks, confirm output format (quick answer / CSV / JSON) and result count.

Standard run (blocking):

apify actors call "ACTOR_ID" --input-file input.json --user-agent apify-agent-skills/apify-ultimate-scraper --json 2>/dev/null

Prefer --input-file input.json for large or complex inputs. For tiny inputs, inline JSON is acceptable with shell quoting: --input '{"maxItems":10}'.

From output: .id (run ID), .status, .defaultDatasetId, .stats.durationMillis

Fetch results:

apify datasets get-items DATASET_ID --user-agent apify-agent-skills/apify-ultimate-scraper --format json

For CSV: apify datasets get-items DATASET_ID --user-agent apify-agent-skills/apify-ultimate-scraper --format csv

Quick answer mode: Fetch results as JSON, pick top 5, present formatted in chat.

Save to file: Fetch results, use Write tool to save as YYYY-MM-DD_descriptive-name.csv or .json.

Large/long-running scrapes:

apify actors start "ACTOR_ID" --input-file input.json --user-agent apify-agent-skills/apify-ultimate-scraper --json 2>/dev/null

Poll: apify runs info RUN_ID --user-agent apify-agent-skills/apify-ultimate-scraper --json 2>/dev/null (check .status for SUCCEEDED).

Step 4: Deliver results

Report: result count, file location (if saved), key data fields, and links:

  • Dataset: https://console.apify.com/storage/datasets/DATASET_ID

  • Run: https://console.apify.com/actors/runs/RUN_ID

For multi-step workflows: suggest the next pipeline step from the workflow guide.

Troubleshooting

Common errors and pitfalls are documented in references/gotchas.md. Read it before running PPE (pay-per-event) Actors.

Files

references/workflows/company-research.md

Company research workflows

Company intelligence profiling for sales or ABM

When: User has a list of target accounts and wants structured firmographic data, ICP signals, and key personnel for outreach or account-based marketing.

Pipeline

  1. Crawl company website -> apify/website-content-crawler

    • Key input: startUrls (company domains), maxCrawlDepth (2), includeUrlGlobs (about, pricing, team, careers, blog)

  2. Enrich with LinkedIn company data -> harvestapi/linkedin-company

    • Pipe: company name or LinkedIn URL extracted from WCC text -> Actor input

    • Key input: company identifier, includeEmployees: false

  3. AI extract structured signals (n8n: OpenAI node outputs JSON schema with companySize, industry, techStack, keyPersonnel, painSignals)

  4. Store in Supabase, Airtable, or HubSpot with AI-extracted fields as custom properties

Output fields

WCC: text (per page), url LinkedIn: employeeCount, industry, headquarters, description, specialties AI-extracted: companySize, industry, techStack, keyPersonnel, painSignals

Gotcha

WCC crawl at depth 2 can return 20-50 pages per company. For large batches, set maxCrawlPages: 5 focused on the About and Pricing pages via includeUrlGlobs. This keeps cost and latency manageable without sacrificing signal quality.

Startup scouting from Product Hunt

When: User wants weekly discovery of recently launched or funded startups in a target category for investor outreach, partnership, or competitive tracking.

Pipeline

  1. Scrape Product Hunt launches -> apify/web-scraper

    • Key input: startUrls (Product Hunt today/weekly/topic pages), maxCrawlPages (3-5)

    • Note: no dedicated Actor exists - search apify actors search "product hunt" --user-agent apify-agent-skills/apify-ultimate-scraper for community options

  2. Filter by category + upvote threshold (n8n: Filter node on extracted upvotes, category)

  3. Crawl company sites -> apify/website-content-crawler

    • Pipe: results[].website -> startUrls

    • Key input: maxCrawlPages (3), includeUrlGlobs (about, team)

  4. LinkedIn founder lookup -> harvestapi/linkedin-profile-search (by name + company)

    • Pipe: extracted founder names from step 3 -> search input

  5. AI ICP scoring (n8n: OpenAI node scores each startup against defined criteria)

  6. Output to Airtable pipeline + Slack alert for top matches

Output fields

Step 1: title, tagline, upvotes, website, makers[].name, makers[].profileUrl WCC: text, url LinkedIn: fullName, headline, profileUrl, currentCompany

Gotcha

Product Hunt ranking changes throughout the day. Schedule the scrape for end-of-day (11 pm UTC) to capture final vote counts. For AngelList/Wellfound, no maintained public Actor exists - use apify/website-content-crawler on search result pages as a fallback.

Sales meeting prep from LinkedIn and news

When: A calendar event is detected and the user needs a briefing on meeting attendees - their recent activity, company context, and conversation talking points - delivered before the meeting.

Pipeline

  1. Trigger on calendar event (n8n: Google Calendar Trigger, filter for events starting in 30 min)

  2. Extract attendee LinkedIn activity -> harvestapi/linkedin-profile-scraper + harvestapi/linkedin-profile-posts

    • Key input: profiles (attendee LinkedIn URLs), maxPosts (5 recent posts)

  3. Extract company context -> harvestapi/linkedin-company

    • Pipe: results[].currentCompany -> company name

  4. Search recent news -> apify/google-search-scraper

    • Pipe: company name + "news" -> queries

    • Key input: queries, maxResultsPerPage (5)

  5. AI synthesize brief (n8n: OpenAI node produces: key topics, recent signals, suggested talking points)

  6. Deliver via Gmail or WhatsApp node 30 minutes before meeting start

Output fields

Profiles: fullName, headline, recentPosts[], experience[0] Posts: postText, publishedAt, likes, comments Company: description, employeeCount, recentNews Search: organicResults[].title, organicResults[].snippet, organicResults[].url

Cost estimate

All HarvestAPI Actors are PPE. Per meeting with 2 attendees: profile scraper ~$0.02, posts ~$0.01, company ~$0.005, Google search ~$0.01. Total: ~$0.05 per meeting prep.

Gotcha

LinkedIn profile URLs must be in the calendar event description or a linked CRM record - they won't auto-resolve from email addresses. Set up a step in your CRM or calendar template to include LinkedIn URLs for attendees. Without a valid profileUrl, the HarvestAPI Actors return empty results.

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Names Claude Code tools, Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Apify
Publisher
Apify (Official)
Source
apify/agent-skills · skills/apify-ultimate-scraper · commit f22557f
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (written by AutoGineer)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Apify.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download apify-ultimate-scraper.zip