Resources · n8n integration

Google Business Profile n8n integrationAutomate Google Business Profile with n8n.

Reviews and posts stop waiting for someone to open the dashboard. The Google Business Profile n8n integration ships a node with 9 operations across 2 resources, posts and reviews, and a trigger that watches 1 event, Review Added. Built for anyone running listings for more than one storefront.

Try the Google Business Profile integration on n8nSee the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Google Business Profile n8n integration actually do?

Two nodes, both shipped with n8n. The app node calls the Google Business Profile API for you, with 9 operations split between the Post resource and the Review resource. The trigger node watches one location and starts a workflow when a review shows up. Both run on the same Google credential, which is the login you store once in n8n and reuse in every workflow.

Three patterns cover most of what gets built here. Answering every review the same day is the first. The trigger fires on a new review, a model or a canned template drafts the text, and review.reply posts it under the review. Append a line to Google Sheets and the log of what was answered, and when, writes itself.

Running one campaign across many storefronts is the second. Keep a sheet with one row per location, loop over it, and call post.create with Post Type set to Offer, a Coupon Code and a Redeem Online Url. The regional manager edits a spreadsheet, the workflow does the publishing.

Knowing what is still live is the third. A scheduled run pulls the posts with post.getAll and Return All switched on, spots the ones whose End Date has gone by, then refreshes them with post.update or pulls them with post.delete. A short summary in Slack or a digest through Gmail tells the owner what moved.

Anything beyond those 9 operations goes through the HTTP Request node, which calls any endpoint of the Google Business Profile API while reusing the same credential via predefined authentication. Same login, wider surface.

Two things shape the design before you start. The trigger polls, so nothing here is instant: an item appears after the interval you set. And every call names one Account and one Location, so covering a network means iterating over the list rather than passing several at once. Still comparing platforms? The n8n review goes through that, and the n8n training covers the expression syntax used in the notes below.

Connect

How do you connect Google Business Profile to n8n?

  1. 01

    Create the Google credential

    A credential in n8n is a stored login. You create it once under Credentials, and every node that needs it offers it in a dropdown. On n8n Cloud the short path is Managed OAuth2: open the credential screen and click Sign in with Google. Nothing to set up in the Google Cloud Console, nothing to copy across.

  2. 02

    Build a custom OAuth2 app on a self-hosted instance

    Managed OAuth2 is a Cloud feature, so a self-hosted n8n needs a custom OAuth2 credential. Create a Google Cloud Console project, enable the APIs you need, then fill the OAuth consent screen: App name, User support email, and an Audience set to Internal for your own workspace or External for any Google account. Under Branding, add n8n.cloud or your instance domain as an authorized domain.

  3. 03

    Point the node at one location

    Still in Google Cloud, create an OAuth client ID of type Web application, paste the OAuth Redirect URL that n8n displays into Authorized redirect URIs, then carry the Client ID and Client Secret back into the n8n credential. Open the node: Account picks the Google Business Profile account, Location picks the storefront. The trigger asks for the same pair.

Triggers

What starts a Google Business Profile workflow?

Google Business Profile Trigger is the node that starts a workflow when something happens in Google Business Profile. It listens to 1 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Google Business Profile account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

review.*1

    Configuration notes

    01Set up the Google Business Profile TriggerThe trigger node is a separate node from the one that acts. It asks for the same Google credential, then for the profile it should watch, and it hands the rest of the workflow one item per new element it finds.

    The trigger node is a separate node from the one that acts. It asks for the same Google credential, then for the profile it should watch, and it hands the rest of the workflow one item per new element it finds.

    Key parameters

    • Account: the Google Business Profile account, picked from the list the credential fills in.
    • Location: the specific location or business inside that account. One location per trigger node, so a network of storefronts means one trigger per storefront or a scheduled run built on the node instead.
    • Event: the parameter that says what the node listens for. Review Added is the value on offer.
    • Poll Times: how often n8n asks Google whether anything new showed up. Polling means asking on a schedule rather than being told, and the interval goes down to the minute.
    When to use it
    whenever the workflow has to start from what customers do, rather than from a time of day you picked yourself.
    02Review AddedThis is the single event the trigger can react to, and it belongs to the review family. n8n compares what the API returns between two polls and emits one item for each review it had not seen before, which is what the rest of the workflow reads.

    This is the single event the trigger can react to, and it belongs to the review family. n8n compares what the API returns between two polls and emits one item for each review it had not seen before, which is what the rest of the workflow reads.

    Key parameters

    • Event: set to Review Added, the value reviewAdded in the workflow JSON.
    • Location: the review stream is scoped to the storefront you chose, so a multi-site brand keeps one branch per site.
    Use cases
    a dental practice pipes each new review into a model that drafts an answer, a human approves it in a chat message, and review.reply sends it. A hotel group routes anything short and negative to the duty manager before anyone writes a public response.
    When to use it
    for reaction, not for backfill. Pulling the reviews already sitting on a location is a job for review.getAll, run once.
    Actions

    What can the Google Business Profile node do, operation by operation?

    The Google Business Profile node exposes 9 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

    Resources × operations matrix
    ResourceCreateGetGet ManyUpdateDeleteReply
    Post✓✓✓✓✓
    Review✓✓✓✓

    Post

    5 operations
    01

    Create post

    post.create

    What you see in n8n

    Notes & use cases

    Publishes a post on the location you selected. The type picked reshapes the form below.

    Key parameters

    • Post Type: Standard, Event, Offer or Alert. An Event asks for Start Date and Time and End Date and Time, an Offer for Start Date and End Date as YYYY-MM-DD, an Alert for an Alert Type whose sub-type is Covid 19.
    • Summary and Title: the body of the post and its headline, the "Sales this week" kind.
    • Options: a Call to Action Type (Book, Call, Learn More, Order, Shop, Sign Up) with its Call to Action Url, plus Coupon Code and Terms and Conditions.
    Use cases
    a coffee chain pushes the same weekend offer to every storefront from one spreadsheet row.
    02

    Delete post

    post.delete

    What you see in n8n

    Notes & use cases

    Removes a published post from the location. What the call needs is the post itself, not the text it carried.

    Key parameters

    • Post: the selector that names which post goes. Pick it from the list, or switch the field to expression mode and feed the identifier carried by the incoming item with {{ $json.field }}.
    • Account and Location: the profile and the storefront the post belongs to.
    Use cases
    a seasonal offer gets pulled the morning after it ends, from a nightly schedule that reads the end dates.
    03

    Get post

    post.get

    What you see in n8n

    Notes & use cases

    Reads one post back and returns its details. Useful before you decide whether to edit it or take it down.

    Key parameters

    • Post: the same selector as the delete and update calls, which lets a workflow chain read, check, then act.
    • Location: the storefront that owns the post, inside the Account the credential unlocked.
    Use cases
    a Monday check confirms that the promotion a store manager published on Friday is the one actually showing.
    04

    Get many posts

    post.getAll

    What you see in n8n

    Notes & use cases

    Lists the posts of a location and hands the workflow one n8n item per post, ready to filter or write out.

    Key parameters

    • Return All: switched on, n8n keeps requesting the next page of the API until every post of the location is in.
    • Limit: what applies when Return All stays off, capping how many posts come back in a single run.
    Use cases
    a weekly inventory of what is published across a franchise network, dumped into a sheet so head office can see gaps.
    05

    Update a post

    post.update

    What you see in n8n

    Notes & use cases

    Edits a post that is already out there rather than replacing it. Everything editable sits in the Options collection.

    Key parameters

    • Post: which published post gets rewritten.
    • Options: Summary, Title, Language, the event pair Start Date and Time and End Date and Time, the offer pair Start Date and End Date, plus Coupon Code, Redeem Online Url and Terms and Conditions.
    • Call to Action Type: the same list as on create, where Get Offer is flagged deprecated in favour of an Offer post.
    Use cases
    pushing a store event back by a week is a date change, not a new publication.

    Review

    4 operations
    06

    Delete a reply to a review

    review.delete

    What you see in n8n

    Notes & use cases

    Takes back the answer attached to a review. The review stays where it is, the reply under it goes.

    Key parameters

    • Review: required here, the selector that names the review whose reply gets removed.
    • Account: the profile the review belongs to, alongside the Location that received it.
    Use cases
    an automated answer that went out with the wrong branch name is cleared, then sent again correctly by Reply to review.
    07

    Get review

    review.get

    What you see in n8n

    Notes & use cases

    Fetches a single review from a location and returns its details, one item out.

    Key parameters

    • Review: the review to read. In expression mode, point the field at the identifier travelling on the incoming item with {{ $json.field }}.
    • Location: the storefront the review was left on.
    Use cases
    pull the full review before handing it to a model, so the draft answers what the customer actually wrote instead of a summary of it.
    08

    Get many reviews

    review.getAll

    What you see in n8n

    Notes & use cases

    Reads the reviews of a location in bulk, one item per review. This is the operation behind exports and backfills.

    Key parameters

    • Limit: required on this operation, it sets the maximum number of reviews a run brings back.
    • Return All: turn it on and n8n chains the API pages until the whole set is through, which is what an export needs.
    Use cases
    a monthly dump into a sheet so a multi-location team reads a full quarter of feedback in one place instead of clicking through profiles.
    09

    Reply to review

    review.reply

    What you see in n8n

    Notes & use cases

    Posts the public answer under a review, which is the end of most review workflows.

    Key parameters

    • Reply: the body of the response, up to 4096 characters. Wire a drafted text in with {{ $json.field }}.
    • Review: which review receives the answer, inside the chosen Location.
    Use cases
    the trigger catches a new review, a model drafts three sentences in the brand voice, a human approves in a chat message, this operation sends it.
    Need help

    Need help automating Google Business Profile with n8n?

    A person reads every message.

    FAQ

    Google Business Profile and n8n: common questions

    01Is the Google Business Profile n8n integration free?
    Yes on the n8n side. Both the node and the trigger ship with n8n, so there is nothing to install and no add-on to buy, on n8n Cloud as well as on a self-hosted instance running the Community Edition under the Sustainable Use license. A workflow behaves the same in both places, so you can prototype on Cloud and move the same JSON onto your own server later. What a Google Business Profile account itself costs is outside the scope of this page. The only other thing you need is a Google Cloud account, which is what the OAuth credential is built on.
    02What credentials do you need for the Google Business Profile node?
    A Google OAuth2 credential for a single service. On n8n Cloud, Managed OAuth2 handles it: click Sign in with Google in the credential screen and nothing else has to be configured. Self-hosted instances build a custom OAuth2 credential instead, which means a Google Cloud Console project, enabled APIs, a configured consent screen, and a Client ID plus Client Secret pasted into n8n. A Service Account is the other documented route, using the Service Account Email and the Private Key taken from the client_email and private_key entries of the downloaded JSON file. OAuth2 is the recommended one: more widely available and easier to set up. Create the credential once and both the node and the trigger pick it up.
    03What are the limits of the Google Business Profile node in n8n?
    The node exposes 9 operations across 2 resources, posts and reviews, and each call names one Account and one Location, so a network of storefronts means looping over a list rather than passing them all at once. On the read side, Get Many Posts and Get Many Reviews return up to Limit items unless Return All is switched on, in which case n8n chains the API pages until everything is through. For an endpoint of the Google Business Profile API that sits outside those operations, the HTTP Request node calls it directly while reusing the same credential through predefined authentication, so you stay on one login.
    04Does the Google Business Profile trigger work in real time?
    No, it polls. n8n asks the Google Business Profile API at the interval you set in Poll Times, compares what comes back, and emits one item per new element it finds. The shortest interval is one minute, and the delay between a customer leaving a review and your workflow running is that interval. There is no webhook to register on the Google side, which also means nothing to maintain there. If a reply has to feel immediate, poll every minute and keep the workflow short. If a daily digest is enough, a wider interval cuts the number of calls for nothing lost.
    05n8n or Make for Google Business Profile?
    It comes down to hosting and cost model rather than features. n8n runs on your own server, via Docker or npm, or on n8n Cloud, and the same workflow behaves the same way in both. Make is hosted only, with no self-hosting option, and billing is per operation, so a workflow that loops over many locations and many reviews changes the bill as volume grows. If review data has to stay inside infrastructure you control, self-hosting settles it. If nobody on the team wants to run a server, hosted wins. Both give you a visual canvas, so try the flow you actually need on each and judge the logic, not the screenshots.
    Hack'celeration Lab

    Get our weekly integration tips.

    No spam. Unsubscribe anytime.

    Same platform

    Other docs you might need on this stack.

    Browse all integrations