This is the heavier version allowing you to display unlimited reviews.
This guide walks you through connecting your Google Business Profile (GBP) reviews to the Limecube Reviews widget. You’ll create one small Apps Script “proxy” in your own Google account, enable the right Google APIs, and paste three values into the widget.
This element is accessible by going to the Integrations element → Google Reviews - Full
You will paste these into the Limecube Google Reviews element:
This guide walks you through connecting your Google Business Profile (GBP) reviews to the Limecube Reviews widget. You’ll create one small Apps Script “proxy” in your own Google account, enable the right Google APIs, and paste three values into the widget.
You will paste these into the widget: (1) Proxy Endpoint URL, (2) Google Business Account ID, (3) Google Business Location ID.
The GBP APIs are not enabled by default. You must submit an access request to Google and receive approval for your Google Cloud project before you can read reviews via the API.
business.manage scope.console.cloud.google.com.All the points below happen from the left side bar in Google Cloud, starting from: https://console.cloud.google.com/apis/credentials/consent

https://console.cloud.google.com/apis/credentials/consent
https://www.googleapis.com/auth/business.manage.If verification is requested, ensure the logo, authorised domain, home page, privacy policy, terms, and support email are all set as above, then follow Google’s prompts.
https://www.googleapis.com/auth/business.manage and click 'Add to table'. That will add it to the table above and have it pre-selected.Open a new tab (leave the Google Cloud tab open)
Return back to your Google Cloud tab.
https://script.google.com/macros/d/SCRIPT_ID/usercallbackSCRIPT_ID with the Script ID you copied in Step A.Tip: If you later see a redirect_uri_mismatch error, it means the URI above doesn’t exactly match the one saved on the OAuth client. Edit the client and fix the URI.
OAUTH_CLIENT_ID in the first 'Property field → and paste your Client ID into the 'value field'.OAUTH_CLIENT_SECRET in the first 'Property field → and paste your Client secret into the 'value field'.The friendliest way is Google’s OAuth 2.0 Playground.
https://www.googleapis.com/auth/business.manage
And paste into the field next to the 'Authorize APIs' button.GET https://mybusinessbusinessinformation.googleapis.com/v1/accounts
name like locations/123...):
GET https://mybusinessbusinessinformation.googleapis.com/v1/accounts/ACCOUNT_ID/locations?pageSize=100&readMask=name,title
You now have: Account ID and Location ID.
Minimum Star Rating
Maximum Number of Reviews
Scroll Speed (pixels per second)
Hover Slowdown Factor
Proxy Endpoint URL
/exec).Google Business Account ID
Google Business Location ID
name (e.g., from locations/6723368497723051295 paste 6723368497723051295).Date Format
dd/MM/yyyy → 12/05/2025, MMM dd, yyyy → May 12, 2025.<YOUR_WEB_APP_URL>?action=listReviews&accountId=<ACCOUNT_ID>&locationId=<LOCATION_ID>&max=3
reviews array. Example: {
"reviews": [
{ "rating": 5, "comment": "Great!", "updateTime": "2024-11-10T03:12:45Z", ... },
{ "rating": 4, "comment": "Very good", ... }
]
}
“Authorization is required” page, or HTTP 401/403
https://www.googleapis.com/auth/business.manage.“Invalid redirect URI” during Google sign-in/consent
This appears while completing the OAuth consent. Fix by aligning the OAuth client’s redirect URI with your Apps Script project.
https://script.google.com/macros/d/<SCRIPT_ID>/usercallback
“CORS has been blocked” error in the browser console
Open DevTools (F12) and check the Console for CORS messages. The Limecube widget uses JSONP to avoid CORS, so you should not see this if your deployment is correct.
callback parameter (JSONP). Example: <YOUR_WEB_APP_URL>?action=listReviews&accountId=...&locationId=...&max=3&callback=cb123
Empty reviews array (no errors)
HTTP 404 or TypeError from Apps Script
ContentService or response handling.HTTP 429 or intermittent timeouts
Try using searching below: