Resources · Make integration

Google Programmable Search Engine Make integrationAutomate Google Programmable Search Engine with Make.

Need search results inside an automation instead of a browser tab? The Google Programmable Search Engine Make integration gives you 1 action, Query Google Search. This page shows builders how to connect the API key, then chain a first scenario around it.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Google Programmable Search Engine Make integration do?

It lets a Make scenario (the automation you build, a chain of modules) send a query to the Programmable Search Engine you set up in Google, then hand what comes back to the next step. There is one module, an action, so something else always starts the flow: another app or a schedule.

Lead research without copy and paste. A sales team gets a new company name from a form or a CRM. Query Google Search runs a search on that name, and the next module writes the answer where the rep will read it.

Topic watch for a content team. A scheduled scenario queries the search engine on the subjects the team follows and passes the results to a sheet or a chat app, so nobody has to repeat the same search by hand.

Fact checks inside a support flow. When a ticket mentions a product or a site, the scenario searches it first and attaches what it found before an agent opens the ticket.

What the integration does not do: it has no trigger, no search module besides this action, and no Make an API Call module for requests the action does not cover. Make's own documentation for this app also warns that it was generated with AI and may contain mistakes, so check anything important against Google's documentation. If you are new to Make, the Make training covers the editor from zero. Weighing another tool? Read n8n vs Make. And when a run fails, Make troubleshooting walks through the usual causes.

Connect

How do you connect Google Programmable Search Engine to Make?

  1. 01

    Collect your two keys in Google

    Open the Programmable Search Engine control panel, create an engine or pick an existing one, and copy the Programmable Search Engine ID from the Basic section of its Overview page. Then copy an API key from the Custom Search JSON API documentation or the Google Cloud Console.

  2. 02

    Add the module and open the connection

    In your scenario, add the Query Google Search module and click Create a connection. A connection is your Google account linked to Make once, then reused by every module of this app.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when you run several engines. Paste the credentials you copied in Google, or follow the on-screen instructions, and save.

First scenario

Your first scenario with Google Programmable Search Engine

GoalWhen a new company name shows up in another app, Make runs a Google Programmable Search Engine query on it and passes the result along.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. That first module comes from another app, such as the form or CRM where company names appear.

  2. 02

    Set up the starting module

    Pick that app, create its connection, and fill its fields. Once connected, Make lists what it can read there, so you choose from a list instead of typing IDs.

  3. 03

    Add Query Google Search

    Click the + on the right of the first module, search for Google Programmable Search Engine, pick Query Google Search, and select the connection you created earlier.

  4. 04

    Map the search terms

    Map the company name from the first module into the search. Each bundle (one item passed between modules, here one company) runs its own query.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can read the search output before going further.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the Google Programmable Search Engine module does

Google Programmable Search Engine gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Need help

Need help automating Google Programmable Search Engine with Make?

A person reads every message.

FAQ

Google Programmable Search Engine and Make: common questions

01Is the Google Programmable Search Engine Make integration free?
Yes, on the Make side. It is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, and up to 5 minutes per execution. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Google is a separate matter: the Programmable Search Engine service has its own subscription, and Make's documentation sends you to Google's pricing page for it.
02What do you need to connect Google Programmable Search Engine to Make?
Two items from Google and a Make account. First, a Programmable Search Engine that is already configured; its ID sits in the Basic section of the Overview page in the control panel. Second, an API key, which you copy from the Custom Search JSON API documentation or the Google Cloud Console. In Make, you add the module, click Create a connection, optionally name it, and paste those credentials. Both values come from Google, so keep them somewhere safe and reuse them.
03Can Google Programmable Search Engine trigger a Make scenario in real time?
No. The app has no trigger at all, only the Query Google Search action. To start a scenario, use the trigger of another app, for instance a form or a CRM that notices a new record, or put the scenario on a schedule. A new scenario runs every 15 minutes by default; the Free plan cannot go below that interval, while paid plans can go down to 1 minute. Test the whole chain with Run once before you switch it on.
04What if the Google Programmable Search Engine module in Make does not cover what you need?
Then Make offers no fallback inside this app. There is no Make an API Call module here, so you cannot send a custom request to Google through the same connection. Look at whether another app in Make covers the step you are missing, or ask the team for help designing the scenario. Keep in mind that Make's documentation for this app says it was AI-generated and may contain errors, so confirm details with Google.
05Should you use Make or n8n for Google Programmable Search Engine?
It depends on where the rest of your automations already run. In Make, this app gives you one action, Query Google Search, available from the Free plan, and your scenario needs another app or a schedule to start it. If your other scenarios live in Make, keeping the search there avoids splitting your work across two tools. If your team works in n8n, check what that tool offers for the same app before deciding.