Skip to content

Google Business Profile

Google Business Profile channels post updates to one of your business locations through the UmbHost.Automate.GoogleBusiness package and its Create Google Business Update action (googleBusiness.createUpdate).

dotnet add package UmbHost.Automate.GoogleBusiness

Each site uses its own Google Cloud project and its own API access. UmbHost doesn’t need access to your project, and your updates never pass through UmbHost.

  1. You need a Google account that is an owner or manager of the business profile, and the profile must be verified. A location that isn’t verified can’t post updates.

  2. In the Google Cloud console, create a project for the site.

  3. Request access to the Business Profile APIs with Google’s access request form, giving the project number. Google reviews each request, and says to allow 14 days. You’ll get an email when it’s approved; until then, the APIs answer with a quota of zero.

  4. Once access is approved, open APIs & Services → Library in the project and enable the Google My Business API, the My Business Account Management API, the My Business Business Information API and the My Business Verifications API.

  5. Under APIs & Services → OAuth consent screen, set up the consent screen, and add the scope https://www.googleapis.com/auth/business.manage.

  6. Under APIs & Services → Credentials, choose Create credentials → OAuth client ID, with Web application as the type. Add the authorised redirect URI https://<your-site>/umbraco/automate/oauth/callback/googlebusiness, then copy the client ID and client secret.

  7. Add them to configuration, under the name GoogleBusiness:

    {
    "Umbraco": {
    "Automate": {
    "Providers": {
    "GoogleBusiness": { "ClientId": "<client ID>", "ClientSecret": "<client secret>" }
    }
    }
    }
    }

    Keep the secret out of appsettings.json in source control, in user secrets or an environment variable (Umbraco__Automate__Providers__GoogleBusiness__ClientSecret). The package asks for the business.manage scope itself, with offline access, so its tokens renew automatically. Without a ClientId, the Google Business Profile provider is skipped, and UmbSocial doesn’t offer Google Business Profile.

Automate → Connections → Create → Google Business Profile → Authorize, signed in with the Google account that manages the profile.

Validate checks the connection and lists your locations, one per line, as the location’s name followed by its id in brackets, for example Cafe Leeds (accounts/111/locations/222). Copy the id, starting with accounts/, of the location the channel should post to. If the account has no locations, Validate warns No locations found: add your business to Google Business Profile first.

Then add the channel as described in Connecting networks.

Option Values Default
locationName The location, as accounts/<id>/locations/<id>, from Validate on the connection. Required. none

Each post goes out as an update (Google’s “Add update”). Events and offers aren’t supported.

Post field Sent as
Text The update’s text, up to 1,500 characters. Google doesn’t state a limit itself; 1,500 is the widely reported one, and it will be confirmed when the live test is done.
Link URL The update’s button. Without one, the first link in the text becomes the button, so that link must be a full https:// address.
Button The button’s label: Learn more (the default), Book, Order online, Buy, Sign up or Call now. Choose it under Network extras in the composer. Call now rings the business’s phone number, so it needs no link.
Image Optional. Google fetches it from your site, so the site must be reachable from the internet. UmbSocial sends a JPEG.
Image alt text Not sent: Google’s updates have no alt text.
Link title and description Not sent.

UmbSocial checks these rules before a post is saved:

  • The button is one of these (option.invalid:google-business:callToAction).
  • When the post has no link of its own, the first link in the text is https (link.button_https_required:google-business), because it becomes the button. See Network limits.

Before posting, the action checks that the location is verified. If it isn’t, nothing is sent, and the post fails with google_business.location_unverified (Failed, safe to retry once the location is verified).

Google has no idempotency key for updates. If the request that creates the update fails without a clear answer, the action doesn’t retry, and UmbSocial records the post as Unknown: check the profile before retrying.