Resources · Make integration

Google Shopping Make integrationAutomate Google Shopping with Make.

Tired of editing Merchant Center products by hand? The Google Shopping Make integration gives you 5 modules: 3 actions and 2 searches. This guide is for store owners and ops people, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Shopping Make integration do for you?

The integration links your Google Merchant Center account to Make, so a scenario (the automation you build, a chain of modules) can create, update, list and delete your Shopping products for you. Each module is one brick of that chain, and nothing here needs a line of code.

A catalog that follows your source. When a product changes in the tool where you keep your inventory, Create or Update a Product pushes the new data to Merchant Center. If the same item already exists there, it gets updated instead of duplicated.

A status check you do not have to run. List Product Statuses pulls the status Merchant Center holds for each product, so a scenario can pass it on to the place your team already reads.

Cleanup of items you stopped selling. List Products finds what sits in the account, and Delete a Product removes an item for good. Anything the listed modules skip can go through Make an API Call, which reuses the same connection.

Keep one limit in mind: this app has no trigger, so a scenario starts on its schedule or from another app. Google Shopping often has an n8n node too; the n8n vs Make comparison helps you pick. Before you build, the Make review and the Make pricing page cover the plans.

Connect

How do you connect Google Shopping to Make?

  1. 01

    Prepare your Merchant Center access

    You need an active Google Merchant Center account. If you plan to use your own OAuth credentials, create them first in the Google API Console under Credentials, then Create Credentials and OAuth client ID, and copy the Client ID and Client secret.

  2. 02

    Open the connection window

    In your scenario, add any Google Shopping module and click Create a connection. A connection is your Google account linked to Make once and reused by every Google Shopping module afterward. The Connection name field is optional.

  3. 03

    Authorize and save

    Paste the credentials you copied, or follow the on-screen instructions. Once saved, the module can read your Merchant Center data and the connection appears in the list for the next module you add.

First scenario

Your first scenario: push a product and check its status

GoalWhen a product row changes in your catalog tool, Make sends it to Google Shopping and then reads back the product statuses.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the module of the app that holds your catalog, since Google Shopping has no trigger of its own.

  2. 02

    Add Create or Update a Product

    Click the + on the right of that first module, search for Google Shopping and choose Create or Update a Product. Select your connection, then map each product value from the bundle (one item passed along) of the first module.

  3. 03

    Read the statuses

    Add List Product Statuses after it. This search can return several bundles, one per product, so you see what Merchant Center now reports about the items you just sent.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Read the bundles each module received and check that the product reached Merchant Center.

  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 is an operation, the unit Make counts on your plan.

Modules

What the Google Shopping modules do

Google Shopping gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Google Shopping1

Create or Update a Product

Action

In MakeCreates or updates product data. If an item with the same channel, language code, product identifier, and target country already exists, this method updates that entry.

Your product lands in Merchant Center with the data you map, and you never have to decide between creating and editing. If an item with the same channel, language, identifier and target country is already there, Make updates it.

When to use it
any time a product changes in the tool you treat as your source of truth.
Watch out
change one of those four identifying values and you get a second product instead of an update.
Google Shopping2

Delete a Product

Action

In MakePermanently removes a product.

This one takes an item out of your Merchant Center account for good, which keeps discontinued products from lingering in your Shopping listings after you stop selling them.

When to use it
right after a product is archived or removed in your store or inventory tool.
Watch out
the removal is permanent, so test with Run once on a single product before you let it loop over a whole search result.
Google Shopping3

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

You get a way to reach any endpoint of the Google Shopping API from your scenario, using the connection you already set up, so a gap in the module list does not stop the build.

When to use it
the four ready-made modules do not cover the request you have in mind.
Watch out
you write the request yourself, so keep the Google documentation open to get the endpoint and its parameters right.
Google Shopping4

List Products

Search

In MakeLists the products in your Merchant Center account.

You get the products stored in your Merchant Center account, each one as its own bundle, ready to be filtered, compared with your catalog or passed to another module later in the scenario.

When to use it
you want to audit what Google holds against what your store actually sells.
Watch out
a search returns zero, one or many bundles, and every later module runs once per bundle, which adds operations.
Google Shopping5

List Product Statuses

Search

In MakeLists the statuses of the products in your Merchant Center account.

Instead of the product data itself, this search brings back the status Merchant Center keeps for each item, so a scenario can report on your catalog health without you opening the Google interface.

When to use it
after a batch of updates, to see how Google now reads the products you sent.
Watch out
pick this module rather than List Products when the status is what you need; the two return different information.
Need help

Need help automating Google Shopping with Make?

A person reads every message.

FAQ

Google Shopping and Make: common questions

01Is the Google Shopping Make integration free?
Yes, on the Make side. Google Shopping is a standard app, available from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes, and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) go down to a 1 minute interval with unlimited active scenarios. Usage is counted in operations per month. Your Merchant Center subscription is a separate matter handled by Google.
02What do you need to connect Google Shopping to Make?
You need an active Google Merchant Center account and authentication credentials. In the scenario, add a Google Shopping module, click Create a connection, give it a name if you like, then enter your credentials or follow the on-screen instructions. For your own OAuth client, go to the Google API Console, open Credentials, create an OAuth client ID, and copy the Client ID and Client secret. If Google asks for a callback URI, use the one given in the Make documentation.
03Can a Google Shopping scenario start automatically?
Yes, but not from Google Shopping itself, because the app has no trigger module. You have two ways in. The first is the schedule: set the clock on the first module and the scenario runs every 15 minutes by default, or at the interval your plan allows. The second is to open the scenario with a trigger from another app, such as the tool where your product catalog lives, and chain the Google Shopping modules behind it.
04What if a Google Shopping module is missing in Make?
Use Make an API Call. It calls any endpoint of the Google Shopping API from your scenario with the connection you already have, so you are not limited to the 5 listed modules. You write the request yourself, following the Google documentation. Also note that the Make documentation for this app warns that it is AI-generated from Google's official documentation and may contain mistakes, so check important details with Google before relying on them in production.
05Should you use Make or n8n for Google Shopping?
It depends on the tool your team already works in. Make offers Google Shopping as a standard app with 5 modules, a visual editor and a Make an API Call module for the rest. The same app often has an n8n node as well, so both routes can work. Compare how each tool fits your existing scenarios, your team habits and the modules you actually need, and pick the one you will keep maintaining.