Export Reviews to Google Sheets, Power BI and BigQuery

None of the three big review platforms ships a native Google Sheets, Power BI or BigQuery connector. Trustpilot, G2 and Google all publish review data, and all three expect you to move it yourself. There are exactly three routes that work: a CSV export from the dashboard, a scheduled API pull into a table you own, or a review platform that exports the whole set for you on a schedule. Which one is right depends on a single question, whether this is a report you build once or a dashboard that has to stay current.

Does Trustpilot, G2 or Google have a Google Sheets integration?

No, not in the sense people mean when they search for it. There is no connector you authorize once that keeps a tab of reviews up to date. What each platform gives you instead is either a manual CSV download or an API, and the gap between those two is where every one of these projects lives. Here is the honest state of it, checked 15 August 2026.

That last one surprises people most. Google Business Profile has no download control for reviews anywhere in its interface, which is why the question keeps getting asked. The routes out of Google specifically are covered here, including the Takeout mistake that hands you the reviews you wrote about other businesses instead of the ones your customers left about you.

Route 1: the CSV export, for a report you build once

If someone has asked for a review analysis this quarter, stop reading about APIs. A CSV download takes four minutes and lands in Sheets, Excel, Power BI and BigQuery without a single credential.

On G2, the export lives in Review Management. G2's own documentation gives the path as selecting Download CSV from the Reviews found table, with one warning worth reading twice: "Active filters impact the reviews included in your export. You should confirm your filter selections before downloading your review data." People export a filtered view, see 40 rows where they expected 400, and conclude the export is broken. It is not, the filter is still on.

Once you have the file, each destination takes it directly. In Google Sheets it is File, then Import, then Upload. In Power BI Desktop it is Get data, then Text/CSV. In BigQuery it is a load job into a new table, and the one thing worth doing carefully is the schema: let the review date land as a timestamp rather than a string, because fixing that later means reloading the table.

Route 2: a scheduled API pull, for a dashboard that stays current

This is the real project, and it is worth doing only when the data has to be live. Both Trustpilot and Google expose review endpoints, and both gate them.

Trustpilot's public endpoints authenticate with an API key passed as an apikey header, and the private ones, the endpoints that also return the customer email address and order ID behind each review, need an OAuth 2.0 token. Before any of that, you need the API module on your account. The full endpoint map, the plan gating and the documented rate limits are here. Google's side works differently again: the Business Profile API returns every review for a profile you own but access is a manual application, and the Places API returns a maximum of five reviews no matter what you pass it.

The Google Sheets trap nobody mentions

Almost every guide to this suggests IMPORTDATA. It will not work. Google's own reference defines IMPORTDATA as importing "data at a given url in .csv (comma-separated value) or .tsv (tab-separated value) format", and it sends no custom HTTP headers. Review APIs return JSON and require an authentication header, so the function fails on both counts at once. You will get an error or an empty cell, and no indication why.

The function that does work is Apps Script. UrlFetchApp.fetch accepts a headers option, so you can send the API key, parse the JSON response and write rows into the sheet, then attach a time-driven trigger to run it nightly. That is roughly forty lines of code and it is the honest answer to "how do I connect Trustpilot reviews to Google Sheets". There is no formula-only version.

Power BI and BigQuery

Power BI is friendlier here, because Web.Contents in Power Query accepts custom headers, so an authenticated review endpoint can be a real data source with a scheduled refresh on top. The catch is credential handling in the service rather than the desktop app, which is where most of these reports stall on the way to production.

BigQuery is the right destination when reviews need to join to something else, usually orders or support tickets. The pattern that holds up is a small scheduled job writing raw JSON into a staging table and a view flattening it, rather than trying to model the schema perfectly on the first load. Once the reviews are sitting next to revenue in a warehouse, the questions people ask of them turn out to be ad hoc rather than dashboard-shaped, which is when it helps to be able to ask the table a question in plain English instead of writing a new query every time someone wonders whether one star reviews cluster around a particular SKU.

Route 3: let a review platform do the exporting

The third option is to stop treating each platform as a separate integration. A review platform that already holds connections to Google, G2 and Trustpilot can export the combined set on a schedule, which collapses three approval processes, three credential stores and three refresh jobs into one file or one feed. That is the version most teams actually want when they start this, they just describe it as a Google Sheets connector because that is the shape the request arrived in.

It is also the version that survives a staff change. A scheduled Apps Script written by one developer becomes an orphan the moment they leave, and the report quietly goes stale for months before anyone notices the dates stopped moving.

Three rules that break these pipelines

Every failure mode in this work comes from one of three places, and all three are documented by the platforms themselves.

Do not pull from your website's frontend. Trustpilot's rate limiting guidance says to avoid pulling review data directly into your website's frontend, because the page then calls the API on every single view. This is aimed at display code, but the same instinct produces a Sheets formula that refires on every recalculation and burns the allowance for the same reason.

Review text is not yours to warehouse indefinitely. Google's Places policies exempt the place ID from caching restrictions and pointedly do not exempt review content. A reviews table that fills up over years and never expires anything is a terms problem, not just a storage one.

Respect the ceilings. Trustpilot asks that you stay under 833 calls per 5 minutes and 10,000 calls per hour, and suggests webhooks over polling wherever the platform supports it. A nightly sync sits nowhere near those numbers. A dashboard that refreshes every time someone opens it does not.

How do I connect Trustpilot reviews to Google Sheets?

Write an Apps Script that calls the Trustpilot API with your key in an apikey header, parses the JSON and writes rows to the sheet, then set a time-driven trigger to run it on a schedule. There is no native connector and no spreadsheet formula that can do it, because IMPORTDATA handles only CSV and TSV and cannot send authentication headers. The no-code alternative is a scheduled CSV export from a platform that already holds the connection.

Can I connect G2 reviews to BigQuery?

Yes, through a file rather than a live connection. Download the CSV from the Reviews found table in G2 Review Management, then run a BigQuery load job into a staging table. G2 publishes no native BigQuery connector, so a recurring feed means either scripting the download or using a platform that exports your G2 reviews alongside your other sources on a schedule.

Can I connect Trustpilot reviews to Power BI?

Yes, and Power BI is the easiest of the three destinations for a live connection. Power Query's Web.Contents accepts custom headers, so a Trustpilot endpoint plus your API key works as a data source with scheduled refresh on top. You still need API access on your Trustpilot plan first, which is sold as an add-on rather than included, so confirm that before scoping the report.

How fresh does review data actually need to be?

Nightly is enough for almost every review dashboard, and hourly is enough for the rest. Reviews are not a high-frequency data source, and the value of a review arriving in a report six hours sooner is close to zero. The exception is alerting on negative reviews, where minutes matter, and that is a different job entirely. For that, use monitoring that watches the sources and notifies you rather than a spreadsheet that refreshes on a timer.

Can I export another company's reviews?

Only what is public, and not much of it. Trustpilot's public endpoints will return a business unit's public profile and reviews, and its Data Solutions API is built for broader database access. Google caps you at five reviews for a business you do not own. Tools that promise a competitor's full review history are scraping, which sits outside the platforms' terms, and the data they return is not licensed for you to republish anywhere.

The short version

For a one-off analysis, download the CSV and stop there. For a live dashboard, budget an Apps Script or a Power Query source and check your plan actually includes API access before you promise a delivery date. For anything ongoing across more than one platform, the per-platform integration route costs more in maintenance than it looks like on day one, which is the argument for having one system hold the connections and hand you a single export. If the underlying goal was only ever to show reviews on your website, none of this applies, and a single feed across all your review sources gets you there without a credential in sight.