Fixing Google Reviews Automation: Enable the Right API and Harden Your n8n Agent

This error is a common gatekeeper: Google reports "API has not been used in project ... or it is disabled" when the Business Profile (formerly Google My Business) API is not enabled for the Cloud project owning the credentials. Start by verifying the exact API (Business Profile API vs legacy My Business), enabling it in the Google Cloud Console, and confirming the OAuth consent screen, scopes (for example business.manage), and the project that issued the Client ID/Secret match the resources your n8n instance is using.

Beyond the single toggle, there are several operational details that cause repeat failures in production. Ensure refresh tokens are being persisted and rotated correctly, confirm the redirect URI configured in Google matches n8n's callback, and check quota/usage limits and service account vs OAuth account differences - Business Profile endpoints typically require a user OAuth flow rather than a simple service account impersonation. Also validate that scopes are minimal and approved in enterprise G Suite/Workspace admin settings if accounts are managed.

For enterprise deployments, instrument the workflow with explicit validation steps: preflight API calls after credential creation, automated health checks, and clear fallbacks when the review agent cannot publish (for example queue for human moderation). Log the full OAuth exchange audit trail in a secure, tamper-evident store to simplify troubleshooting without exposing secrets.

Leaders should treat review automation as both a customer experience and a compliance vector. Build approval workflows for auto-replies to avoid policy or brand-safety incidents, set rate limits and escalation policies, and invest a small amount upfront in credential hygiene and observability - that reduces incident time-to-detect from hours to minutes and keeps automated responses aligned with brand and regulatory obligations.