Google Business — how to connect

Publishes text updates (up to 1 500 characters) to your Google Business Profile locations via OAuth. Add your GCP OAuth client ID and secret below, then connect — note that the Business Profile API requires explicit allow-listing by Google before calls succeed.

Google Business Profile publishing needs a Google Cloud OAuth client (Client ID + secret) plus separate Business Profile API access approval from Google — that approval is not instant, so plan for several days to weeks before the first location can actually publish.

Before you start

A Google Business Profile that is verified and has been active for 60+ days — Google's manual approval for the Business Profile API checks this, plus a legitimate business use case and a working business website (developers.google.com/my-business/content/prereqs).
Owner or Manager role on the target location(s) under the Google account you connect with — the connect flow lists every (account, location) pair the authorizing user can manage, and locations without at least Manager access won't appear.
A Google Cloud project with the Business Profile API (and Account Management API) access-request submitted and approved — until Google grants it, calls to mybusiness.googleapis.com/v4 and mybusinessaccountmanagement.googleapis.com return 403/quota-0, even with a valid OAuth token.
GOOGLE_BUSINESS_CLIENT_ID and GOOGLE_BUSINESS_CLIENT_SECRET from that same Cloud project's OAuth client, entered in this integration's config before starting Connect.

Step by step

1
Confirm you qualify before starting
You need a Google Business Profile that has been verified and active for 60+ days, with a real business website listed on it — Google checks this before granting API access.
Open
2
Create a Google Cloud project and OAuth consent screen
In Google Cloud Console, create (or pick) a project, configure the OAuth consent screen, and enable the Business Profile APIs for that project.
Open
3
Create OAuth 2.0 credentials
Under APIs & Services > Credentials, create an OAuth client ID (Web application type) and copy the generated Client ID and Client secret.
Open
4
Submit the Business Profile API access request
Fill out Google's official GBP API access request form with your Cloud project number, business use case, and website, then wait for Google's approval — calls will return 403 until this clears.
Open
5
Paste the Client ID and Client secret into the app
In this app's Google Business config, enter the two OAuth app-level values labeled "Client ID" and "Client secret" (the latter stored as a secret) exactly as shown in Cloud Console.
6
Connect an account and grant the business.manage scope
Click Connect, sign in as an owner/manager of the Business Profile, and approve the single requested scope (https://www.googleapis.com/auth/business.manage) — the app then lists every location the token can manage as a separate connected account.

App keys (set once in Settings)

Client ID
Google Cloud Console → APIs & Services → Credentials → your OAuth 2.0 Client ID (Web application type). Also submit the Business Profile API access request — calls 403 until Google approves it (days to weeks).
Client secretsecret
Same OAuth 2.0 client → "Client secret". From the same Cloud project whose Business Profile API access was approved.

Good to know

Approval gate is real and outside your control: every new Cloud project starts with zero quota for Business Profile APIs, and access requests typically take days to weeks — the adapter surfaces this as a 403 until Google approves.
You must be an owner/manager of the Business Profile you connect; the account used for OAuth consent needs manage access to the target location(s).
Only the single shared scope business.manage is requested — there is no per-location scope selection.
Text posts (Local Posts) are capped at 1,500 characters; the adapter truncates automatically, and media/metrics are not yet supported by this adapter.
If no locations are returned after connecting, it usually means the API access request is still pending rather than a misconfiguration.
Google may separately verify your OAuth consent screen/app is configured correctly, which can add its own review delay.

Troubleshooting

Connect finishes OAuth but immediately fails with "No Google Business locations found for this account (access may be pending approval)".: Your GCP project's Business Profile API access request hasn't been approved yet (or Account Management API quota is still 0 QPM) — check quotas for these APIs in Cloud Console; approval takes days to weeks, not instant. This is unrelated to whether the profile itself is verified.
Publishing or listing locations returns HTTP 403 "Request had insufficient authentication scopes" / PERMISSION_DENIED.: The token was minted without the business.manage scope (or against the wrong OAuth client). Reconnect via this integration's Connect button so the app requests https://www.googleapis.com/auth/business.manage fresh — don't reuse a token generated for a different Google API/product.
Connect works and locations list, but every post publish call 403s specifically on the v4 localPosts endpoint even though accounts/locations calls succeed.: Account Management and Business Information APIs can be approved separately from the older v4 My Business API that local posts still use — confirm your project's access request explicitly covers Business Profile Content/local posts, not just account/location read access.
Everything worked before, now publish fails with 401 or the connection shows expired/disconnected.: The refresh token was revoked or the access token expired without a valid refresh token stored (offline access wasn't granted, or the user revoked app access in their Google Account). Disconnect and reconnect with Connect so consent is re-prompted and a new refresh token is captured.

Google Business developer docs

Before you start

A Google Business Profile that is verified and has been active for 60+ days — Google's manual approval for the Business Profile API checks this, plus a legitimate business use case and a working business website (developers.google.com/my-business/content/prereqs).

Owner or Manager role on the target location(s) under the Google account you connect with — the connect flow lists every (account, location) pair the authorizing user can manage, and locations without at least Manager access won't appear.

A Google Cloud project with the Business Profile API (and Account Management API) access-request submitted and approved — until Google grants it, calls to mybusiness.googleapis.com/v4 and mybusinessaccountmanagement.googleapis.com return 403/quota-0, even with a valid OAuth token.

GOOGLE_BUSINESS_CLIENT_ID and GOOGLE_BUSINESS_CLIENT_SECRET from that same Cloud project's OAuth client, entered in this integration's config before starting Connect.

Step by step

Confirm you qualify before starting

You need a Google Business Profile that has been verified and active for 60+ days, with a real business website listed on it — Google checks this before granting API access.

Open

Create a Google Cloud project and OAuth consent screen

In Google Cloud Console, create (or pick) a project, configure the OAuth consent screen, and enable the Business Profile APIs for that project.

Open

Create OAuth 2.0 credentials

Under APIs & Services > Credentials, create an OAuth client ID (Web application type) and copy the generated Client ID and Client secret.

Open

Submit the Business Profile API access request

Fill out Google's official GBP API access request form with your Cloud project number, business use case, and website, then wait for Google's approval — calls will return 403 until this clears.

Open

Paste the Client ID and Client secret into the app

In this app's Google Business config, enter the two OAuth app-level values labeled "Client ID" and "Client secret" (the latter stored as a secret) exactly as shown in Cloud Console.

Connect an account and grant the business.manage scope

Click Connect, sign in as an owner/manager of the Business Profile, and approve the single requested scope (https://www.googleapis.com/auth/business.manage) — the app then lists every location the token can manage as a separate connected account.

App keys (set once in Settings)

Client ID

Google Cloud Console → APIs & Services → Credentials → your OAuth 2.0 Client ID (Web application type). Also submit the Business Profile API access request — calls 403 until Google approves it (days to weeks).

Client secretsecret

Same OAuth 2.0 client → "Client secret". From the same Cloud project whose Business Profile API access was approved.

Good to know

Approval gate is real and outside your control: every new Cloud project starts with zero quota for Business Profile APIs, and access requests typically take days to weeks — the adapter surfaces this as a 403 until Google approves.

You must be an owner/manager of the Business Profile you connect; the account used for OAuth consent needs manage access to the target location(s).

Only the single shared scope business.manage is requested — there is no per-location scope selection.

Text posts (Local Posts) are capped at 1,500 characters; the adapter truncates automatically, and media/metrics are not yet supported by this adapter.

If no locations are returned after connecting, it usually means the API access request is still pending rather than a misconfiguration.

Google may separately verify your OAuth consent screen/app is configured correctly, which can add its own review delay.

Troubleshooting

Connect finishes OAuth but immediately fails with "No Google Business locations found for this account (access may be pending approval)".

Your GCP project's Business Profile API access request hasn't been approved yet (or Account Management API quota is still 0 QPM) — check quotas for these APIs in Cloud Console; approval takes days to weeks, not instant. This is unrelated to whether the profile itself is verified.

Publishing or listing locations returns HTTP 403 "Request had insufficient authentication scopes" / PERMISSION_DENIED.

The token was minted without the business.manage scope (or against the wrong OAuth client). Reconnect via this integration's Connect button so the app requests https://www.googleapis.com/auth/business.manage fresh — don't reuse a token generated for a different Google API/product.

Connect works and locations list, but every post publish call 403s specifically on the v4 localPosts endpoint even though accounts/locations calls succeed.

Account Management and Business Information APIs can be approved separately from the older v4 My Business API that local posts still use — confirm your project's access request explicitly covers Business Profile Content/local posts, not just account/location read access.

Everything worked before, now publish fails with 401 or the connection shows expired/disconnected.

The refresh token was revoked or the access token expired without a valid refresh token stored (offline access wasn't granted, or the user revoked app access in their Google Account). Disconnect and reconnect with Connect so consent is re-prompted and a new refresh token is captured.