Google Business Profile Publishing

The local SEO surface most businesses never get around to — turned into a by-product of publishing a blog post, behind an OAuth token minted on every run.

Client
EpsolDev
Category
Automation Engineering
Completed
2026-08-15
Built with
n8n, Google Vertex AI, REST API
Topics
API Development, Automation
Google Business Profile Publishing

n8n 40 nodes Local SEO Publishing daily

The smallest of the five, and the one that is not really social media at all. A Google Business Profile post is local SEO surface — it shows up beside the map listing, for people already searching for the business.

The whole Google Business Profile workflow: generation, the OAuth exchange, and the post-and-verify tail

Part of the Social Distribution Network; its ranking counterpart is the Local Rank Tracking API.

Forked from Instagram, and it still shows

Dispatch, the site loop, the schedule gate and the claim gate

The shared front half is identical to the rest of the set — and the evidence that these five graphs share one ancestor is sitting in plain sight in this one. The per-site schedule gate here is still named:

Parse Config -> IG Due? -> CBM Claim Run

IG Due?, in the Google Business workflow. It was forked from the Instagram graph and the node kept its name. A node name is documentation whether you intended it or not It behaves correctly — it reads this platform's own schedule config — but anyone reading the graph at 3am has to work that out.

Generation, unchanged

Caption and image generation with primary and fallback branches

Caption and image, each with a primary attempt, a wait, and a fallback attempt, converging on Prep Image or exiting through Gen Failed. Identical in shape to Facebook and Instagram, because the generation problem does not vary by platform — only publishing does.

The image round-trips through the content platform's media library for a public URL, exactly as Instagram and Facebook do, and is deleted after the post is confirmed.

The OAuth tail

The credential fetch, token exchange, post creation and verification

Like YouTube and unlike the Meta platforms, Google mints a short-lived access token from a stored refresh token on every run:

GMB Get Creds -> GMB Parse Creds -> GMB Creds OK?
                                          │
                                   GMB Token Exchange -> GMB Token OK?
                                                               │
                                                        GMB Create Post -> GMB Verify
                                                                                │
                                                                       CBM Media Delete
                                                                                │
                                                                        CBM Record Post

Two gates, GMB Creds OK? and GMB Token OK?, both exiting to the site loop. A client whose Google connection has lapsed is skipped silently on that cycle rather than failing the run for every other client in the batch.

Why it is worth automating at all

A Google Business Profile post is small — a picture, a short caption, a link. It is also the single piece of content most businesses never get around to publishing, because it sits outside every content calendar they already keep.

This pipeline makes it a by-product of publishing a blog post. The same topic, the same brand voice, the same run — one more surface, at no extra human cost.

Stack

n8n Google Business Profile API OAuth 2.0 Google Vertex AI Imagen JavaScript REST API

All projects