Skip to main content

Overview

The ScrapeGraphAI app for Make.com lets you connect any automation scenario to ScrapeGraph’s v2 API — no code required. Fetch pages, extract structured data with an AI prompt, run web searches, kick off multi-page crawls, and schedule monitors, all as native Make modules.

ScrapeGraphAI on Make

Install the app from Make’s marketplace

ScrapeGraphAI Dashboard

Get your API key

Installation

  1. Open your Make.com workspace and go to Connections.
  2. Search for ScrapeGraphAI and click Install.
  3. When prompted, enter your SGAI-APIKEY from the dashboard.
  4. Click Save — the connection is shared across all modules in your scenario.
ScrapeGraphAI connection dialog in Make

Example: Extract product data into Google Sheets

This scenario runs daily, extracts all products from an Amazon search page, and saves each one as a row in Google Sheets — no code required. Full scenario flow:
Full scenario: Schedule → Extract → Iterator → Google Sheets
Step 1 — Schedule trigger: Set the scenario to run daily (or any interval). Step 2 — Extract module: Configure with your target URL, an extraction prompt, and an output schema.
Extract module configuration
  • URL: The product listing page to extract from
  • Extraction Prompt: Extract all products on the page with their name, price, rating, and number of reviews
  • Output Schema (JSON):
Step 3 — Iterator: Add a Flow Control → Iterator module and set the Array field to {{2.json.products}}. This loops through each product and passes it to the next module one at a time.
Iterator module configuration
Step 4 — Google Sheets: Add a Row: Map each field from the Iterator output:
  • Name{{value.name}}
  • Price{{value.price}}
  • Rating{{value.rating}}
  • Reviews{{value.reviews}}
Google Sheets module configuration
Result: Every product on the page is saved as a separate row.
Google Sheets result with extracted product data

Modules

Scrape a URL

Fetch a URL and return its content in one or more formats: Markdown, HTML, links, images, a plain-text summary, or branding elements.
Scrape a URL module configuration

Extract data from URL

Send a URL, raw HTML, or markdown to ScrapeGraph and get back structured JSON — driven by a natural-language prompt and an optional JSON schema.
Extract data from URL module configuration

Search web

Run a web search and get page content returned inline — optionally with AI extraction applied to each result.
Search web module configuration

Crawl a website

Start a multi-page crawl from an entry URL. The module polls internally and returns the completed crawl in a single bundle — a pages array with one entry per crawled page, each carrying a scrapeRefId you can pass to Get a past result to fetch its full content.
Crawl a website module configuration
Output:
Crawl a website module output bundle
The bundle includes the Crawl Job ID, a Status of completed, and a pages[] array. Each page has url, depth, title, contentType, status, and scrapeRefId.
Crawls can take a while on large sites. The module waits for completion before emitting its bundle — for very large crawls (hundreds of pages), increase your scenario’s execution timeout in Scenario settings.

Create monitor

Schedule ScrapeGraph to fetch a URL on a recurring cron schedule and detect changes between runs.
Create monitor module configuration
Common cron expressions
Run Create monitor once manually to set up the monitor, then use Get monitor activity in a separate scheduled scenario to fetch what changed.

Get monitor activity

Fetch the latest activity ticks from an existing monitor.
Get monitor activity module
Returns a ticks array where each entry has changed (boolean), diffs, status, and createdAt.

Update monitor

Edit an existing monitor’s interval, format, webhook, or fetch config without deleting and recreating it.
Update monitor module configuration
Any field left blank is left unchanged on the monitor. Returns the updated monitor record.

Get a past result

Fetch a stored job result by its ID. Most useful for retrieving the full content of a crawled page using the scrapeRefId from Crawl a website.
Get a past result module configuration
Returns the full stored entry — result (the original response payload), metadata (content type and other run details), params (the inputs the job was run with), service, status, and createdAt.
Combine Crawl a website → Iterator → Get a past result to crawl a site and retrieve the full markdown / HTML / extracted JSON for every page in one scenario. Map the iterator’s scrapeRefId into the Entry ID field — the module runs once per crawled page.

List past results

Browse recent ScrapeGraphAI jobs filtered by service type. Search-style module — emits one bundle per entry, ready to fan out into downstream modules.
List past results module configuration
Each emitted bundle has id, service, status, url, createdAt, and other run metadata. Pipe a bundle’s id into Get a past result to retrieve the full stored payload.

Fetch Config

Five modules — Scrape a URL, Extract data from URL, Search web, Crawl a website, and Create monitor — accept an optional Fetch Config collection that controls how each page is fetched. Leave it empty to use defaults.
Fetch Config collection expanded inside the Extract module
Reach for Stealth + Mode = JS + Wait = 2000–5000 when a site blocks bots or only renders content after JavaScript runs. Combine with Country to bypass region-locked pages.

Deprecated modules

The following modules from the v1 integration are still visible but no longer functional. Use the v2 modules above instead.