GBP API Automation Skill — Bulk GBP Management with Claude
Updating holiday hours across 85 restaurant locations takes 3 minutes per location through the GBP dashboard. That’s over 4 hours of tedious, error-prone clicking — and someone has to do it again for every holiday. Pushing a new promotional post to 50 retail locations means 50 separate logins, 50 image uploads, 50 copy pastes. At scale, manual GBP management isn’t just inefficient — it’s operationally impossible.
The gbp-api-automation skill bridges the gap between what enterprises need to do and what humans can reasonably execute. It equips Claude to design bulk update workflows using the Google Business Profile API, turning hours of manual work into minutes of automated execution.
What This Skill Does
The gbp-api-automation skill enables Claude to design bulk update workflows for large GBP portfolios, generate API call structures for common operations (hours updates, description changes, photo uploads, post publishing), build validation logic to catch errors before they propagate, and guide OAuth setup and API access configuration.
Prompt: "I need to update holiday hours for Christmas Eve, Christmas Day,
and New Year's Day across all 85 of our restaurant locations via the GBP API.
Design the workflow and give me the API call structure."
Skills fired: dispatch → gbp-api-automation
Output:
WORKFLOW DESIGN
1. Pre-flight: Pull current special hours via businessProfiles.locations.list
to establish baseline and identify any locations with existing conflicts
2. Batch structure: GBP API supports batch requests of up to 10 locations
per call. 85 locations = 9 batch calls.
3. API endpoint: businessProfiles.locations.patch
Resource: locations/{locationId}
Field: specialHours
4. Request body structure:
{
"specialHours": {
"specialHourPeriods": [
{
"startDate": {"year": 2024, "month": 12, "day": 24},
"openTime": {"hours": 11, "minutes": 0},
"closeTime": {"hours": 18, "minutes": 0}
},
{
"startDate": {"year": 2024, "month": 12, "day": 25},
"isClosed": true
},
{
"startDate": {"year": 2024, "month": 12, "day": 31},
"openTime": {"hours": 11, "minutes": 0},
"closeTime": {"hours": 22, "minutes": 0}
}
]
}
}
5. Error handling: Log each location response. If any location fails,
continue with remaining batches and retry failed locations separately.
6. Verification: After completion, run locations.list to confirm all 85
locations show correct special hours.
RATE LIMIT CONSIDERATION
GBP API allows 10 requests per second. With batching, this workflow
completes in under 10 seconds plus network latency.When Manual GBP Management Breaks Down
The threshold where API automation becomes essential varies by operation type and portfolio size.
10 locations: Manual management is tedious but possible. Holiday hours updates take 30-40 minutes. Errors creep in but are catchable.
25 locations: Manual management becomes a significant time investment. Holiday hours take 1-2 hours. Post deployment across all locations takes most of a day. Consistency errors increase.
50+ locations: Manual management is operationally infeasible for any non-trivial update. A portfolio-wide description update would take an entire week of clicking. The probability of errors approaches 100%.
100+ locations: API automation isn’t optional — it’s the only way to maintain the portfolio. Manual updates are reserved for emergency single-location fixes.
The ROI calculation is straightforward. If a holiday hours update takes 3 minutes per location manually, 85 locations require 4.25 hours of staff time. API automation completes the same update in minutes. Across multiple holidays and updates per year, the time savings compound dramatically.
Beyond time savings, API automation provides consistency. Manual updates introduce human error — typos in hours, forgotten locations, inconsistent formatting. API updates apply identical changes to all locations reliably.
GBP API Architecture: What You Need to Know
The GBP API (formerly Google My Business API) provides programmatic access to most GBP management functions. Understanding its structure helps you design effective automation workflows.
Authentication: The API uses OAuth 2.0. You create credentials in Google Cloud Console, authenticate with the appropriate scopes, and receive access tokens that authorize API calls. For automated workflows, service account authentication enables server-to-server access without interactive login.
Account hierarchy: The API operates on an account → location hierarchy. Your Google account has access to one or more GBP accounts. Each GBP account contains locations. API calls target specific locations within this hierarchy.
Key API components:
- Business Information API: Read and update location data (hours, description, categories, attributes)
- Posts API: Create and manage GBP posts
- Reviews API: Read reviews (writing reviews via API is not supported)
- Verification API: Handle verification flows
Rate limits: The API has daily quotas and per-minute rate limits. Standard quotas are generous for most portfolios, but extremely large operations (500+ locations) may need to pace requests or request quota increases.
The gbp-api-automation skill understands this architecture and generates workflows that respect hierarchy, authentication, and rate limits.
Common Bulk Automation Workflows
Certain operations benefit most from API automation.
Holiday hours: The most common bulk automation use case. Christmas, Thanksgiving, Fourth of July, New Year’s — each requires special hours across all locations. API automation pushes these updates in minutes.
Description updates: Brand messaging changes, promotional language updates, or seasonal description modifications across all locations. The API updates descriptions uniformly while allowing location-specific variables (city name, address).
Category audits and corrections: When primary or secondary categories need adjustment portfolio-wide, API automation ensures consistent changes.
Attribute standardization: Ensuring all locations have consistent attributes (payment methods, accessibility features, service options) checked and unchecked.
Bulk post deployment: Promotional posts, seasonal content, or brand announcements published to all locations simultaneously. The Posts API enables programmatic post creation with location-specific variables.
Photo refresh campaigns: Uploading new brand photos, seasonal images, or updated facility photos to all locations. The Media API handles bulk photo uploads.
Error Handling and Validation
Bulk operations that fail partway through create inconsistent portfolio states — some locations updated, others not. Robust automation includes error handling.
Pre-flight validation: Before executing updates, validate that all target locations exist, are accessible, and have the expected current state. Catch problems before they propagate.
Transaction logging: Log every API call with location identifier, request content, and response status. When something fails, the log identifies exactly what happened.
Graceful degradation: If one location fails, continue processing remaining locations. Don’t let a single-location error abort the entire batch.
Retry logic: Transient failures (network timeout, rate limit hit) should retry automatically. Persistent failures (invalid location, permission denied) should log and skip.
Post-run verification: After batch completion, query all locations to verify the updates applied correctly. Identify any discrepancies for manual review.
The skill generates workflows with these patterns built in, preventing the “85 locations, 84 updated, which one failed?” nightmare.
Setting Up GBP API Access
API access requires Google Cloud Console configuration.
Step 1: Create a Google Cloud project or use an existing one.
Step 2: Enable the Google Business Profile API for your project.
Step 3: Configure OAuth consent screen with appropriate scopes.
Step 4: Create credentials (OAuth client ID for interactive applications, service account for server-to-server automation).
Step 5: Link your GBP account to the Cloud project through the API settings.
Step 6: Test authentication with a simple read operation (list locations) to confirm access.
The skill can guide each step with specific console navigation and configuration details.
API vs. Third-Party Platform: When to Use Each
Not every portfolio needs direct API implementation. Third-party platforms abstract API complexity.
Use direct API when: You have development resources, need custom workflows beyond standard features, manage 100+ locations with complex operations, or want maximum control over automation logic.
Use third-party platforms (BrightLocal, Uberall, Yext, etc.) when: You want managed services without development investment, need additional features beyond API scope (reputation management, citation building), prefer dashboards over code, or manage 10-50 locations where platform fees are justified by time savings.
For agencies, the calculus includes client billing: API development is a one-time investment that scales across clients; platform fees are recurring per-client costs.
Get Started
For bulk operation planning:
I need to [specific operation] across [number] locations via the GBP API.
Design the workflow, show me the API call structure, and include error
handling for a production implementation.For API setup guidance:
Walk me through setting up GBP API access for a [number]-location portfolio.
I need [specific operations] capability. What credentials and configuration
do I need?Claude will generate complete workflow designs, API call structures, and implementation guidance tailored to your portfolio requirements.
Learn More
To learn what this skill can do for your local SEO workflow, see the skill overview.