Skip to content

Put scraped website data into Google Sheets with Make

This guide builds a no-code flow that fetches a blog listing page, extracts each post, and writes one row per post to a spreadsheet. It is useful when you want a repeatable collection without writing a script, and when the page structure is stable enough for selector-based extraction.

What you will build

You will learn to scrape blog posts from a website and push the scraped content into Google Sheets. The example targets a blog listing and collects post title, author name, post introduction and published date as the intended fields, while the concrete extraction rule in the example returns link, title and description for each post. Decide your final column set before you build the sheet, because the header row and the field mapping must match.

Prepare the spreadsheet first

Prepare three accounts: the scraping service, Make, and Google. In Google Sheets, create a spreadsheet with a header row containing link, title and description for this example. Keep the spreadsheet name easy to find later, because you will select it from a dropdown inside Make.

Create the scenario and the API call

Sign in to Make and open your dashboard. Create a new scenario, then add the first module and search for the scraping app. A scenario is a chain of modules that show how data moves and changes between services. Choose the Make an API call module as the trigger step, because the job starts by requesting a page rather than waiting for an event.

Connect and configure the request

Add a connection for the scraping service and enter the API key from its dashboard. Make connections handle authentication for services that need it. Then set the request method to GET, which is the normal browser method for displaying a page. Enter the blog URL you want to watch in the URL field. POST is for submitting forms and is not needed here.

Add extraction rules

Tick Show advanced settings, scroll to Extract Rules (JSON), and paste the supplied rule from protected module code0001. That rule treats each post card as one list item and pulls the link from the anchor href, the title from the heading, and the description from the paragraph block. If you change the target site, update the selectors to match its markup; extraction rules rely on CSS selectors, so unfamiliar selectors need care. Optionally set Render JS to No when JavaScript rendering is not required, since the example notes it costs extra credits.

Test before you automate the sheet

Use Run Once at the bottom of the page to test the scrape before adding the sheet step. Check that the response contains a list of posts with the expected fields. Fix the URL, connection or selectors at this stage, because later steps will multiply any error across every row.

Split the list with an Iterator

Add a Flow Control module and choose Iterator. An Iterator splits a large bundle into smaller bundles, outputting each array item separately so later modules receive items one after another. Point it at the posts array from the scrape response, shown in the example as Body then Posts. Without this step, a single list response cannot become one spreadsheet row per post.

Write one row per post

Add a Google Sheets module after the Iterator and choose Add a Row. Because it sits after the Iterator, it will add a row for each post. Create the Google connection, which redirects you to Google to grant Make access to part of your account. Select the spreadsheet you created earlier, then select the sheet tab, usually Sheet1 by default. Under values, map the Iterator fields to the columns in the same order as your header row. Run the integration again and confirm the values appear in the spreadsheet.

Quick checklist

Before a final run, check these points: the header row matches the mapped fields, the Iterator points at the correct array, the spreadsheet and tab selections are correct, and Render JS is off unless the page needs it. If rows are missing, re-test the API call alone; if rows are malformed, check the selectors and the field mapping first.

Frequently asked questions

How do I tell the scraper which fields to return?

Use a GET request to the target URL, enable advanced settings, and supply extraction rules that describe the repeated item and the fields inside it. In the worked example the repeated item is a post card, and the fields are its link, title and description.

Why is an Iterator needed before writing to the sheet?

An Iterator turns one array response into separate bundles, one per item. Placing the sheet-writing step after it means that step runs once for each post instead of trying to write the whole list at once.

What should I check before the final run?

Create the spreadsheet first with a header row matching your fields, then in the sheet module choose that spreadsheet and the correct tab, map each scraped field to its column, and run the scenario again to check the rows appear.

{
  "posts" : {
    "selector": "a.shadow-[0px 2px 20px rgba(169, 169, 169, 0.16), 0 32px 46px -27px rgba(117, 117, 117, 0.2)]",
    "type": "list",
    "output": {
      "link": {
        "selector": "a",
        "output": "@href"
      },
      "title": "h4.font-bold.mb-[12px]",
      "description": "Example post details.",
    }
  }
}