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.
89 articlesPage 1 of 9
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.

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.

Connect Apify's remote MCP server (https://mcp.apify.com) to Claude Cowork as a custom connector, then ask Cowork in plain language to scrape a site. Cowork picks the right Apify Actor, runs it, and hands you the data to export as a spreadsheet, no code.
Claude Cowork is Anthropic's "hand Claude real work" surface: it runs on the same agentic engine as Claude Code but with no terminal, so it can take on multi-step tasks and finish them for you. Cowork can already search the web and, with computer use, drive a browser a page at a time. What it has no answer for is bulk structured extraction: paginating a result grid, holding a schema across thousands of rows, rotating proxies, and surviving anti-bot defences. That is exactly what Apify adds: a store of pre-built scrapers Cowork can call as tools.
This guide connects the two and turns "get me this web data" into a spreadsheet, with no code.
Create a free Apify account (free monthly credits) →

Scrape Trustpilot reviews with an Apify Trustpilot Actor: paste a company's Trustpilot URL (or its domain), set how many reviews and which star ratings you want, run the Actor, and export the ratings, review text, dates, and company replies as JSON or CSV. No coding required.
Trustpilot is where customers rate companies at scale, so its reviews are a goldmine for reputation monitoring, competitor benchmarking, and product research. The site's UI paginates and caps what you can see, and it has no export button, which is exactly the gap a scraper fills.
This guide covers no-code Trustpilot extraction on Apify: which Actor to pick, the input fields that matter, what it costs, and how to turn the review text into insight with an LLM.
Start on Apify (free monthly credits) →

Scrape Google reviews with Apify's Google Maps Reviews Scraper: paste the business's Google Maps URL, set how many reviews you want, run the Actor, and download review text, ratings, dates, and owner replies as JSON or CSV. No coding required.
Google reviews are one of the richest public signals a business leaves behind: star ratings, written feedback, dates, and the owner's replies. Pulling them at scale lets you monitor reputation, track sentiment over time, and benchmark competitors, none of which the Google Maps UI lets you export.
This guide walks through no-code review extraction with the Apify Google Maps Reviews Scraper (used by more than 48,000 people), the input fields that matter, what it costs, and how to turn the raw text into insight with an LLM.
Start on Apify (free monthly credits) →

TL;DR
- One
docker-compose.yml: n8n + LiteLLM + Twenty CRM + shared PostgreSQL + Redis + Caddy
- Measured idle RAM: ~1.7 GB; peak: ~2.5 GB (parallel workflow executions with live LiteLLM calls)
- Minimum Liquid Web tier: 8 GB Managed VPS (~$33–$40/mo)
- Zapier Pro + unmanaged OpenAI API + HubSpot Starter: ~$69 + variable + $50/mo vs ~$33/mo self-hosted
Most sales teams that want AI-augmented automation end up in one of two bad places: paying for Zapier Pro, a direct OpenAI API key they can't audit, and HubSpot CRM — three separate subscriptions that don't compose well and bill regardless of usage. Or they write fragile Python scripts that break on every API change and nobody wants to maintain.
This guide deploys the middle path: Twenty CRM for pipeline management, n8n for visual workflow automation, and LiteLLM as an OpenAI-compatible AI proxy — all on a single Liquid Web 8 GB VPS. n8n calls LiteLLM for every AI task (lead enrichment summaries, proposal draft generation, inbound form classification), and LiteLLM provides budget caps, model fallbacks, and a unified request log.

"Agentic AI" is not just for enterprise. In April 2026, small and medium businesses can deploy practical AI agents using no-code tools — agents that qualify leads, answer support questions, schedule content, chase invoices, and monitor inventory.
This playbook covers five agents built with tools you can set up without a developer: Claude, Make.com, n8n, Apify, and Google Sheets. For Model Context Protocol (MCP) setups that connect Claude to your tools (see the "Claude Desktop + MCP" guide in Next steps below), the same agent ideas apply once data and actions are wired in.
TL;DR:
| Agent | What it does | Setup tool | Time to deploy |
|---|
| 1. Lead Qualifier | Scores inbound leads, routes to sales or nurture | Make.com | 2 hours |
| 2. Support Responder | Drafts responses to support emails | Make.com / n8n | 3 hours |
| 3. Content Scheduler | Researches and drafts social media posts | Make.com | 2 hours |
| 4. Invoice Chaser | Sends payment reminders automatically | Make.com / n8n | 1.5 hours |
| 5. Inventory Monitor | Alerts when stock hits reorder thresholds | n8n + Apify | 2 hours |
Prerequisites:
- Make.com account (free tier available)
- Claude: Use Claude API for automation (pay-per-token billing via Anthropic Console — free tier includes limited credits). Claude Pro ($20/mo) is a chat subscription for claude.ai; it does not provide API access for Make.com or n8n HTTP calls.
- Google account (for Sheets, Gmail)
- No coding required for agents 1–4

Enterprise competitive intelligence tools — Crayon, Klue, Kompyte, Similarweb — charge $300–$2,000/month (quote-based, plan-dependent) for competitive monitoring dashboards. This same monitoring can be built with Apify for data collection, Claude for analysis, n8n for orchestration, and a free dashboard — for under $50/month (starting cost; scales with competitor count, Actor fees, and proxy usage).
This guide builds it step by step: from identifying what to monitor, to automated daily scrapes, to AI-powered change detection that alerts your team in Slack when competitors make moves that matter.
TL;DR:
| Component | Tool | Cost |
|---|
| Data collection | Apify (5 competitors, daily) | ~$30/mo |
| Analysis | Claude API (change detection, summarization) | ~$5–15/mo |
| Orchestration | n8n (self-hosted) | $0 |
| Dashboard | Google Sheets or Grafana | $0 |
| Alerts | Slack webhooks | $0 |
| Total | | ~$35–45/mo |