n8n - 💡(How to fix) Fix google sheets oauth error [2 comments, 3 participants]

Describe the problem/error/question

I am seeing what looks like a node-level Google Sheets credential binding bug in n8n.

In the same workflow, multiple Google Sheets nodes are working correctly with the same Google Sheets OAuth2 credential. However, 3 newly added Google Sheets update nodes show an error saying the credential does not exist, even though the credential is present and working in other Google Sheets nodes in the same workflow.

This does not appear to be an authentication issue at the account level. It looks like these specific nodes are referencing a stale or broken internal credential binding.

The affected nodes are used after a webhook + switch flow to update different columns in a Google Sheet based on WhatsApp webhook events such as delivered, read, and failed.

Expected behavior:

• The new Google Sheets nodes should use the same existing Google Sheets credential as the other working Sheets nodes in the workflow.
• They should execute normally without any missing-credential error.

Actual behavior:

• These specific nodes show a tooltip/error that says: "Credentials with name 'Google Sheets account' do not exist for Google Sheets OAuth2 API."

Important context:

• Other Google Sheets nodes in the same workflow are working fine.
• This is the only Google Sheets credential in use.
• So the issue seems isolated to these specific nodes, not to Google Sheets auth overall.

What is the error message (if any)?

Credentials with name "Google Sheets account" do not exist for Google Sheets OAuth2 API.

Also shown in tooltip: You can create credentials with the exact name and then they get auto-selected on refresh.

Please share your workflow/screenshots/recording

Workflow summary:

• Main workflow sends WhatsApp messages and writes initial log rows into Google Sheets.

• Webhook workflow receives Interakt status callbacks.

• Webhook payload is parsed in an Edit Fields node.

• A Switch node routes events into branches:

  • delivered
  • read
  • failed

• Each branch uses a Google Sheets update node to update the existing row in the WA Logs sheet.

The problem is only with the 3 Google Sheets update nodes added after the Switch node. Older Google Sheets nodes in the same workflow are working normally.

Relevant screenshots attached:

• Execution view showing the 3 failing Google Sheets nodes after the Switch node
• Tooltip on the failing node showing the missing credential message

Share the output returned by the last node

The failing nodes do not execute successfully because they stop with the credential error before returning a normal node output.

Working behavior elsewhere in the workflow:

• Other Google Sheets nodes are able to read/update/append successfully using the same credential.

Expected output from the affected nodes:

• Update the matching row in the WA Logs sheet by WA Message ID

• Write values like:

  • Delivery Status = delivered/read/failed
  • Delivered At
  • Read At
  • Failure Reason

Debug info

core

• n8nVersion: 2.13.4
• platform: docker (self-hosted)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: -1
• license: community

storage

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

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-04-08T13:29:22.580Z