use-apify.com
Automation: guides & tutorials
Automate scraping, APIs, and schedules with Apify. Trigger actors, push datasets downstream, and replace manual copy-paste between your stack and sources.
96 articlesPage 1 of 10
View all tags
Web automation handles the repetitive digital work humans should not: extracting data on a schedule, filling forms, routing results between tools, and firing alerts when a price drops or a review appears. These guides show how to build automations that run 24/7 with no babysitting, using no-code tools or custom code.
Non-coders reach for Make, Zapier, or n8n to trigger scrapers and move data visually, while developers use Playwright and Crawlee for browser-level control. Apify sits at the data layer, feeding any automation tool with fresh structured records. Below you will find tutorials for wiring scrapers into workflows, comparisons of automation platforms, and patterns for reliable scheduled runs.

claude -p "<prompt>" runs Claude Code without the interactive UI: it does the task, prints the result and exits. Put that command in a shell script, call the script from cron on a small Linux server, and you have an agent that works overnight. The safe version adds four things: a long-lived token in a chmod 600 file, --permission-mode dontAsk with a short allow list, --max-budget-usd and --max-turns caps, and --output-format json so every run leaves a log with its estimated cost. For web pages that block plain fetches, connect the Apify MCP server with an API token.
Most Claude Code guides stop at the interactive terminal. This one is about the jobs you want done before you sit down: a digest of what changed in the tools you depend on, a refreshed dataset, a report waiting in a folder. The example job below was run for real on 2026-10-21, and the flags, costs and failure modes in this post come from that run and from Anthropic's Claude Code documentation.

Four files turn a folder into a Claude Code research workspace: a CLAUDE.md with sourcing rules, a project-scope .mcp.json that connects the Apify MCP server with only three tools (search-actors, fetch-actor-details, call-actor), a .claude/settings.json that wires a PreToolUse hook to refuse any Actor run without a spend cap of $1 or less, and a /research skill that runs the whole loop. Every file is below, ready to copy.
Most Claude Code setup guides are about writing code. Mine is mostly about reading the web: pulling search results, pages Claude's built-in fetch can't render, and datasets I want to keep. That job has two failure modes code work does not have. Claude can state things it never sourced, and a scraper can quietly spend money.
This setup addresses both. It is a folder you can recreate in five minutes, and it works the same for a solo researcher as for a team that commits it to a repo.

Connect Apify to Claude Cowork, then schedule a daily task that searches Reddit for your brand and competitors with the Reddit Scraper Lite Actor. Claude throws out the false matches, tags the sentiment of the real mentions, and lists the threads where a reply from you would help. In our test, only 1 of 8 Reddit posts that matched a brand search was a real conversation about the product, so the filtering step is the actual job. A daily run of 30 items costs about $0.16 at the Free-plan list price.
Reddit is where people ask "is X worth it?", complain about a pricing change, and recommend tools to strangers. Those threads also get read by AI assistants. In Ahrefs' September 2026 data, reddit.com was the most-cited domain in ChatGPT answers for broad US queries, with 16.8% of citations (Ahrefs, updated 2 September 2026). That share moves around: Semrush saw ChatGPT cite Reddit in close to 60% of responses in early August 2025 and around 10% by mid-September (Semrush, 10 November 2025). The ranking is consistent even when the percentage is not, so an unanswered complaint thread about your product can end up shaping AI answers about you as well.

Set up a Claude Cowork scheduled task that runs once a week. It calls the Google Maps Reviews Scraper on Apify for every location's reviews from the last 8 days, skips the ones you already answered, and drafts a reply for each new one in your brand voice. Anything rated 3★ or lower is put at the top, risky reviews are escalated with no draft, and sudden bursts of reviews are flagged for a human to judge. Claude drafts; you post. Google only publishes a reply when the business posts it from its Business Profile or through Google's own API. For 10 locations the scraping costs well under $1 a week.
Answering every review across ten locations is not hard work. It is tedious work, so it slips: the 5★ reviews get a "thanks!", the 2★ review from three weeks ago never gets an answer, and nobody notices the location whose rating is quietly sliding. A weekly task fixes the slipping part. It reads every new review, writes the first draft, and hands you a single list to approve.

A Claude Skill is a SKILL.md folder that packages instructions Claude loads automatically when relevant. Build one that tells Claude to run Apify Actors for scraping, and every future "get me this web data" request just works. Or install the official Apify Claude Code plugin, which ships five ready-made skills.
Agent Skills are modular capabilities that extend Claude: each Skill packages instructions, metadata, and optional resources that Claude uses automatically when they are relevant to your request. Instead of re-explaining how you like to scrape every time, you encode it once, and Claude reaches for it on its own.
This guide builds a scraping skill that calls Apify, and points you at the official plugin if you would rather not start from scratch.