Resources · Make integration

Looker Studio Make integrationAutomate Looker Studio with Make.

Can Make answer Looker Studio when it asks for fresh data? Yes. The Looker Studio Make integration gives you 7 modules: 1 instant trigger, 4 actions and 2 searches. This guide is for people who build reports and manage who sees them, and it walks you from the connection to a first live scenario.

Try the Looker Studio integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Looker Studio Make integration let you automate?

The Looker Studio Make integration links your Looker Studio account to Make, a no-code tool where you chain modules into a scenario. A module is one brick (a trigger, an action or a search), and a scenario is the automation those bricks form. Here, Looker Studio can call Make for data, and Make can manage who has access to your assets.

Reports that pull data from Make. New Request fires when Looker Studio asks Make for data. Your scenario gathers what the report needs, then New Response hands the result back. A marketing analyst can shape data in Make instead of maintaining a separate export.

Access that follows your team. When a consultant joins a client account, Add Asset Members opens the right asset to them. When the project closes, Revoke Asset Permissions takes that access away, so nobody keeps a view they no longer need.

A clear picture of who sees what. Search Assets finds the assets you care about, and List Asset Permissions returns the members of each one. Send that list to a spreadsheet or a message and review it before an audit.

For anything these modules skip, Make an API Call reaches the rest of the Looker Studio API with the same connection. The documentation gives no numeric limit for this app. If you are weighing tools, the n8n vs Make comparison sets out the criteria, the Make training covers the editor step by step, and Make troubleshooting helps when a run fails.

Connect

How do you connect Looker Studio to Make?

  1. 01

    Add a Looker Studio module

    Open your scenario, click the +, search for Looker Studio and pick any of its modules. In the module panel, click Create a connection. A connection is your Looker Studio account linked to Make once, then reused by every Looker Studio module.

  2. 02

    Name the connection

    This step is optional, but it pays off later. Give the connection a name that tells you which account it uses, such as the client or the team it belongs to. That way you pick the right one without guessing when a scenario grows.

  3. 03

    Authorize Make and save

    Authorize Make: either you sign in on the Looker Studio page and accept, or you paste the key Looker Studio gives you. Use the account that owns the assets you want to manage. Then click Save, and the module can read your assets.

First scenario

Your first scenario with Looker Studio

GoalWhen Looker Studio asks Make for new data, Make searches your assets and sends the list back.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. Search for Looker Studio and choose New Request as the first module.

  2. 02

    Link your account

    Click Create a connection, authorize Make and save. The trigger is instant: Looker Studio calls Make through a webhook each time it asks for data, with no polling in between.

  3. 03

    Add the search

    Click the + on the right of New Request and add Search Assets. Fill its fields; once the connection exists, Make lists what it can read, so you pick instead of typing.

  4. 04

    Send the answer back

    Add New Response after the search and map the data found by Search Assets into it. Each asset found travels as one bundle, meaning one item passed from a module to the next.

  5. 05

    Test, then switch it on

    Click Run once and read the bundles each module received. When the answer looks right, turn the scenario on so Make listens every time Looker Studio sends a request.

Triggers

What starts a Looker Studio scenario

1 module starts a scenario when something happens in Looker Studio. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Looker Studio as soon as it happens.

Looker Studio1New Request

New Request

Instant trigger

In Make“Triggers when Looker Studio requests Make for new data.”

New Request lets a Looker Studio report pull its data from Make. The moment Looker Studio asks for new data, your scenario starts and can collect, clean or combine what the report should show.

How it fires
instant, Looker Studio calls Make through a webhook as soon as the request happens, so nothing waits for a schedule.
When to use it
a dashboard needs figures that live in another app, and a Make scenario is the easiest place to prepare them.
Watch out
the request only gets its answer if the scenario ends with New Response, so never leave that module out.
Modules

What Make can do in Looker Studio

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

Looker Studio1

Add Asset Members

Action

In Make“Adds members to a given Looker Studio asset.”

Add Asset Members gives new people access to a Looker Studio asset without you opening the sharing menu. Each run opens one asset to the members you map from the previous module.

When to use it
a new client contact signs up in your CRM and should see their dashboard right away.
Watch out
the module acts on a single asset per run, so pair it with Search Assets when several assets are involved.
Looker Studio2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call covers what the six other modules do not, by sending your own request to the Looker Studio API with the connection you already set up.

When to use it
you need an endpoint that has no dedicated module and you have read the API reference for it.
Watch out
this module expects you to know the endpoint and its parameters from the API reference, so keep that page open while you fill it in.
Looker Studio3

New Response

Action

In Make“Send data back from Make to Looker Studio.”

New Response closes the loop with Looker Studio: it takes the data your scenario prepared and hands it back to the report that asked for it.

When to use it
as the last module of any scenario that starts with New Request, after the modules that fetch or shape the data.
Watch out
map only the data you want the report to receive, because whatever reaches this module goes back to Looker Studio.
Looker Studio4

Revoke Asset Permissions

Action

In Make“Removes members from a given Looker asset.”

Revoke Asset Permissions removes members from a Looker Studio asset, which keeps access tidy once someone no longer needs it.

When to use it
a freelancer's contract ends or a client account closes, and their dashboards should stop being visible to them.
Watch out
removing access is the whole point of this module, so test with Run once on an asset you control before switching the scenario on.
Looker Studio5

List Asset Permissions

Search

In Make“Retrieves a list of permissions for a given Looker Studio asset.”

List Asset Permissions tells you exactly who can reach a given Looker Studio asset, returning each permission as a separate bundle you can filter or store.

When to use it
before an access review, to write the members of a sensitive report into a spreadsheet.
Watch out
as a search, it can return zero, one or many bundles, and every following module runs once per bundle.
Looker Studio6

Search Assets

Search

In Make“Searches for Looker Studio Assets.”

Search Assets finds the Looker Studio assets that match your search, so later modules know which ones to work on.

When to use it
at the start of a permissions clean-up, to gather every asset for one client before you add or remove members.
Watch out
it can return zero, one or several assets, so check the bundles after Run once before you map anything into the next module.
Need help

Need help automating Looker Studio with Make?

A person reads every message.

FAQ

Looker Studio and Make: common questions

01Is the Looker Studio Make integration free?
Yes, Looker Studio is a standard app, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each module that runs on one bundle counts as one operation, the unit Make tracks on your plan. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios.
02What do you need to connect Looker Studio to Make?
A Looker Studio account and a Make account. The documentation lists no other prerequisite. In any Looker Studio module, click Create a connection, give it a name if you like, authorize Make on the Looker Studio page and click Save. The connection is then shared by every Looker Studio module in your scenarios, so sign in with the account that owns the assets you plan to manage. Once saved, the connection appears in the drop-down of every new Looker Studio module you add.
03Does the Looker Studio trigger in Make react in real time?
Yes. New Request is an instant trigger: Looker Studio calls Make through a webhook as soon as it asks for new data, and the scenario starts right away. There is no polling interval to wait for, unlike scheduled triggers that Make checks on the scenario schedule. The editor shows this with a lightning badge on the module. Switch the scenario on once your Run once test looks right, so each new request reaches Make.
04What if a Looker Studio module is missing in Make?
Use Make an API Call. It sends any request to the Looker Studio API with the connection you already have, so you can reach endpoints that the six dedicated modules do not cover. You will need the API reference to know the endpoint and its parameters. The documentation gives no numeric limit for this app, so there is no documented quota to plan around on the Make side. Start with the dedicated modules first, and switch to the API call only for the gap.
05Should you use Make or n8n for Looker Studio?
It depends on the modules you need. In Make, Looker Studio comes with 7 modules, including an instant trigger that answers report requests and actions to manage asset members, plus Make an API Call for the rest. The same app often has an n8n node too. Compare the list of operations in each tool against your scenario, and choose the one that covers it without workarounds. Neither tool is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations