Google Sheets Trigger not firing automatically on n8n Cloud - credential mismatch between Trigger OAuth2 and Managed OAuth2

The Issue:

WF1 (Ops Organizer + AP Invoice Capture) uses a Google Sheets Trigger node set to poll “Every Minute” watching for new rows in the “Ops Inbox” tab. The workflow is published (green dot) on n8n Cloud v2.13.3.

When I add a new row to the Google Sheet, the trigger does NOT fire automatically. It only works when I manually click “Fetch Test Event” or “Execute Workflow” in the editor.

Root Cause (most likely):

The Google Sheets Trigger node uses a credential called “Google Sheets Trigger OAuth2 API” while all other Google Sheets nodes in the workflow use “n8n.cloud Google Sheets Integration” (Managed OAuth2). These are two different credential types in n8n — they cannot be shared. If the trigger credential was authenticated with a different Google account, or if the OAuth token expired silently, the trigger has no access to the spreadsheet and fails without any error message.

What I’ve Tried:

  • Setting poll time to “Every Minute”

  • Reconnecting the OAuth2 credential

  • Publishing the workflow (green dot confirmed)

  • Deleting and recreating the trigger node

  • The trigger credential only offers “Google Sheets Trigger OAuth2 API” — I cannot select the working “n8n.cloud Google Sheets Integration” credential

What Works:

  • Manual execution (Execute Workflow + Fetch Test Event) works perfectly

  • All downstream nodes (Claude AI extraction, PO matching, Google Sheets write, Payment Ledger) work correctly

  • The “n8n.cloud Google Sheets Integration” credential works fine for reading and writing to

    Google Sheets in other nodes

What I Need: The workflow to automatically detect new rows in the Ops Inbox tab and process them without manual intervention.

Hi @Fernando_Sorokin Welcome!
Have you tried deleting the existing sheets trigger, and replacing it with the same trigger but with managed OAuth2 credential? Let me know how that does..

the oauth credential mismatch is definitely the issue — n8n’s google sheets trigger node can’t share credentials with the regular google sheets integration nodes. have you tried deleting the trigger node and replacing it with a new one that uses the managed oauth2 credential instead? that should fix the polling.

welcome to the n8n community @Fernando_Sorokin !
I think the core solution has already been covered above
Just to add a bit more context, this kind of issue can also happen if the trigger credential has expired or lost access silently (especially with non-managed OAuth setups), which would explain why manual execution still works but polling does not.