Resources · Make integration

Scrapeless Make integrationAutomate Scrapeless with Make.

Need web data in your automations without writing a scraper? The Scrapeless Make integration adds 6 action modules: crawl a site, scrape one page, query Google or Google Trends, unlock protected pages. This guide walks growth and ops teams through the connection and a first scenario.

Try the Scrapeless integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Scrapeless Make integration do for you?

The Scrapeless Make integration lets a Make scenario, the automation you build as a chain of modules, fetch web data for you: one page, a whole site, Google results or Google Trends interest. A module is one brick of that chain. All 6 Scrapeless modules are actions, so something else has to start the scenario.

Pull a competitor's pricing page. Place Scrape data from a single page after the trigger of the tool where your team lists the pages to follow, and each new entry turns into page data you can send to a sheet or a team chat.

Audit a documentation site. Crawl data from all pages follows the links of a site and brings back the data of every page it reaches, a solid base for a content review. When a page resists because it is protected or built by scripts, Unlock a website is the module made for that job.

Check what people search for. Search Google returns result data for a query, and Search Google Trends adds keyword popularity and interest, handy for an SEO lead preparing a brief.

What Make does not do here: Scrapeless has no trigger, so nothing starts on its own when a page changes. You start the scenario from Make's schedule or from another app's trigger. Make's documentation page for this app also warns that it was generated by AI from the Scrapeless docs, so confirm important details with Scrapeless.

Weighing tools? The n8n vs Make comparison sets the two side by side. To build faster, the Make training covers scenarios step by step, and Make pricing details the plans.

Connect

How do you connect Scrapeless to Make?

  1. 01

    Open the connection window

    Add any Scrapeless module to your scenario and click Create a connection. A connection is your Scrapeless account linked to Make once, then reused by all 6 modules. The Connection name field is optional: type a label if you run several accounts.

  2. 02

    Copy your token in Scrapeless

    Log in to Scrapeless and open the section where API keys are managed, usually labeled API or Developer Settings. The key Make needs is called x-api-token. No account yet? Create one first, since Make requires an active account and a token.

  3. 03

    Paste it into Make

    Back in Make, paste the token in the connection window and confirm. Every Scrapeless module in this scenario, and in the next ones, now uses the same connection, so the token never has to be pasted twice.

First scenario

Build your first scenario with Scrapeless

GoalWhen your team adds a page address in the tool it already uses, Make scrapes that page with Scrapeless.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where your team lists pages to follow, such as a sheet or a form.

  2. 02

    Add the Scrapeless module

    Click the + on the right of that first module, search for Scrapeless and choose Scrape data from a single page. Click Create a connection and paste your x-api-token.

  3. 03

    Map the page to read

    In the module, map the page address coming from the first module. Each new entry travels as a bundle, one item passed from module to module, and Scrapeless reads that single page.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and check that the page data came back as expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What each Scrapeless module does

Scrapeless gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Scrapeless1

Crawl data from all pages

Action

In Make“Crawl a website and its linked pages to extract comprehensive data.”

Get the data of a whole site in one pass: the module starts from an address, follows the linked pages and returns what it collects on each of them. It suits a blog, a help center or a catalog you want to review.

When to use it
you need every page of a section, for example to list all articles before a content refresh.
Watch out
for one page only, Scrape data from a single page is the module built for it.
Scrapeless2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any part of the Scrapeless API that the five dedicated modules leave out, with the connection you already created. You write the request yourself, which makes it the most open module and the least guided one.

When to use it
the endpoint you need has no dedicated module in this list.
Watch out
keep the Scrapeless API documentation open while you write the request, and try the dedicated modules first.
Scrapeless3

Scrape data from a single page

Action

In Make“Extract data from a single webpage.”

Bring the content of one page into your scenario, ready to pass to a sheet, a CRM or an AI step. You point it at a single address and that page's data comes back as a bundle.

When to use it
a lead form sends a company website and you want its homepage text to qualify the lead.
Watch out
it reads one page only; to follow links across a site, switch to Crawl data from all pages.
Scrapeless4

Search Google

Action

In Make“Retrieve search result data for any query.”

See what Google shows for a query without opening a browser. The module fetches the result data for the words you give it, so the scenario can store it, compare it or pass it along.

When to use it
a marketer adds a target keyword to a sheet and wants the matching results logged next to it.
Watch out
you get search results, not the pages behind them; add Scrape data from a single page to read one of them.
Scrapeless5

Search Google Trends

Action

In Make“Access popular keyword and interest data from Google Trends.”

Find out how much interest a keyword attracts before you invest in it. This module pulls popularity and interest data from Google Trends straight into the scenario.

When to use it
an editorial team wants to compare several topic ideas before choosing the next article.
Watch out
Trends measures interest, not pages; pair it with Search Google when you also need the actual results.
Scrapeless6

Unlock a website

Action

In Make“Accesses protected or dynamic pages. Handles anti-scraping systems automatically.”

Open pages that block ordinary scrapers or only load their content through scripts. Scrapeless handles the anti-scraping protection for you, so the scenario receives the page rather than a refusal.

When to use it
a site you need keeps turning away Scrape data from a single page, or shows nothing until scripts run.
Watch out
reserve it for the stubborn sites and keep the simpler module for ordinary pages.
Need help

Need help automating Scrapeless with Make?

A person reads every message.

FAQ

Scrapeless and Make: common questions

01Is the Scrapeless Make integration free?
Yes, on the Make side. Scrapeless is a standard app, so its 6 modules work from the Free plan. That plan allows 2 active scenarios, a 15-minute minimum interval between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and lift the cap on active scenarios. Usage is counted in operations, one module run on one bundle. You still need an active Scrapeless account with its own token.
02What do you need to connect Scrapeless to Make?
An active Scrapeless account and its API token. In Scrapeless, the token sits in the API or Developer Settings area under the name x-api-token. In Make, add any Scrapeless module, click Create a connection, name it if you wish and paste the token. That connection is then shared by every Scrapeless module, so the setup happens once. No webhook is involved, because none of the 6 modules is an instant trigger.
03Does Scrapeless trigger Make scenarios in real time?
No. Scrapeless has no trigger module, so it cannot start a scenario by itself. All 6 modules are actions that run when something before them does. You have two ways in: set a schedule on the first module, every 15 minutes by default and never closer than 15 minutes on the Free plan, or place the trigger of another app first, such as a form or a sheet where your team lists pages. Scrapeless then works on each bundle that trigger sends.
04What if a Scrapeless module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Scrapeless API with the connection you already have, so features without a dedicated module stay within reach. Keep the Scrapeless API documentation at hand to write the request. Also note that Make's own page for this app states it was generated by AI from the Scrapeless docs and may contain errors, so confirm important details with Scrapeless before relying on them.
05Should you use Make or n8n for Scrapeless?
It depends on where your automations already live. In Make, Scrapeless offers 6 modules including Make an API Call, a visual editor and a connection created once, which covers scraping, crawling, Google searches and Trends without code. The same app often has an n8n node as well, so check it there if n8n is already your stack. Choose the platform your team runs every day rather than splitting your flows across two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations