All Google OAuth credentials fail on my n8n Cloud workspace with “Salted__ is not valid JSON” error

Hi n8n team,
I’m facing a workspace-level OAuth issue on n8n Cloud.
Problem:
All Google OAuth credentials (Google Sheets, Gmail) fail during authorization with the error:
“Unexpected token ‘S’, ‘Salted__…’ is not valid JSON”
Key details:

  • I am using n8n Cloud (not self-hosted)
  • The issue happens for multiple Google services (Sheets + Gmail)
  • The error appears immediately when clicking “Sign in with Google”
  • The issue persists in Incognito mode
  • Deleting and recreating credentials does not help
  • Creating a new workflow/node does not help
    This seems like an OAuth encryption/decryption issue at the workspace level.
    Request:
    Could someone from the n8n team please reset or repair the OAuth credential encryption for my workspace?
    Happy to provide workspace ID or any additional info if needed.
    Thanks!

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @Tarun_Kumar !

Welcome to n8n community!

Before sending an official request to [email protected] with your workspace ID, in order to create a ticket number, so a staff member who’s willingto assist when is available and can handle that…

Is the app in test mode? Maybe the token expires and needs to be published.

Cheers!

i also have the same issue, i am using n8n cloud

i have encountered this just now

Please help

1 Like

Sir, i tried publishing it too, couple times from different projects and even different google accounts .

It doesn’t work, it throws the same error

Hey @zzyz3 and @Tarun_Kumar .

In this situation, only the n8n tram can help.

Please create a ticket with your workspace ID at the email address provided. HELP.N8N.IO

Ceers!

I’m have similar issues. Earlier today I could no longer reconnect any of my Google Credentials (Drive, Doc, Sheets). Funny thing is that some of my workflow nodes could still connect but the google docs node could not update or append any docs. I spent hours with Claude trying to debug via the MCP connection. My local hosted version of n8n works fine. Something is blocking the n8n.cloud domain. I’m running the latest beta version of cloud n8n (2.1.1) it was having the same issue with the prior version of the beta. I’ve verified in the Google Cloud Console → API & Services Credentials are all correct including the URL redirects. I have a Claude summary of the issue with questions that your support needs to look into in a shared Google Doc –> Click Here.

My n8n instance is: b01e799c8597a418342586f9fe42b57cf7798483b7d7540aea0ab43464ea70a2. Debug info is: Debug info

core

  • n8nVersion: 2.1.1
  • platform: docker (cloud)
  • nodeJsVersion: 22.21.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: enterprise (sandbox)
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-12-18T06:53:54.252Z

1 Like

I found the solution that n8n version should be in stable version not in beta version

2 Likes

I also reverted to the Stable release (2.0.3) and this resolved the OAuth2 issue to Google Docs.

Having the same issue at 2.1.2 which is supposed to be the latest stable version, but it isn’t. And I can’t revert back? Only upgrade to 2.2.0?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.