n8n - 💡(How to fix) Fix Gmail trigger not fetching unread emails

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

Gmail trigger not fetching unread emails.

To Reproduce

  1. Create/Define Google OAuth credentials.
  2. Create a workflow and add Google trigger with default settings.
  3. Select the credentials created above.
  4. Ensure you have unread and read emails from the account used for authentication.
  5. Click on the 'Fetch Event'.

Expected behavior

With Default Settings:

  • should return unread emails

With Read Status 'unread emails':

  • should return unread email

Debug Info

Debug info

core

  • n8nVersion: 2.14.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: community
  • consumerId: 69094d43-551b-4f87-a90a-68482251d633

storage

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

pruning

  • enabled: true
  • maxAge: 1440 hours
  • maxCount: 30000 executions

client

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

Generated at: 2026-04-20T17:21:53.475Z

Operating System

Docker

n8n Version

2.14.2

Node.js Version

24.13.1

Database

Postgress

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

The Gmail trigger may not be fetching unread emails due to incorrect configuration or authentication issues, and verifying the Google OAuth credentials and trigger settings is necessary.

Guidance

  • Check the Google OAuth credentials to ensure they have the correct permissions and are properly configured.
  • Verify that the Gmail trigger is set up correctly, including the selection of the correct credentials and the 'Read Status' option.
  • Test the trigger with different settings, such as changing the 'Read Status' option to 'all emails', to see if it returns any emails.
  • Review the n8n workflow and node settings to ensure they are correctly configured to handle the Gmail trigger output.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be specific to the self-hosted Docker environment or the n8n version (2.14.2), and further investigation may be required to determine the root cause.

Recommendation

Apply workaround: Verify and reconfigure the Google OAuth credentials and Gmail trigger settings, as the issue may be related to authentication or configuration rather than a version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

With Default Settings:

  • should return unread emails

With Read Status 'unread emails':

  • should return unread email

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Gmail trigger not fetching unread emails