Gmail getAll:message Node (Filters: Label & Unread Emails Only) is not working

[kennethMM241]

Bug Description

Here is the 2 images, i tried filtering the 2 selected option, though its not getting the unread emails.

To Reproduce

1. Send an email to someone, and Label it as (Leads)
2. Using the someone email, reply to the message
3. Now go back to your original email and see if someone replied (dont click/view it)
4. Go to the gmail getAll; message node
5. Add filter option
6. Select filter option of 'label names', & 'read email status'
7. Then run the node, if it finds a data good for you though help me, if it doesnt find a data please fix.

Also let say you manually click the read and unread in gmail, technically the gmail node would find the data, but what i need is that no need to click it yet, let the gmail node know it first before you manually click the read and unread.

Thank you very much!

Expected behavior

To get specific unread emails only

Operating System

Windows 10

n8n Version

1.97.1

Node.js Version

20.19.2

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @kennethMM241,

We have created an internal ticket to look into this which we will be tracking as "GHC-2523"

[Jayanth930]

Hi @kennethMM241,

I’ve tested this on my local setup following the same steps you mentioned. I was able to successfully retrieve the Gmail messages, including those marked as unread with the specified label. Additionally, I tested both scenarios:

1.Received the email and ran the action without opening it — the node successfully returned the results.
2.Opened the email, marked it as unread, and then executed the action — the node still returned the expected results.

Here are the screenshots showing the results:

My environment details:

Operating System: macOS Sequoia 15.5

n8n Version: 1.98.0

Node.js Version: 22.16.0

Database: SQLite (default)

Execution Mode: main (default)

Let me know if there's a specific case I might’ve missed or if your Gmail setup differs in any way. Happy to dig deeper if needed!

Thanks!

[Joffcom]

Thanks for reporting this issue! We’ve attempted to reproduce the problem, but unfortunately, we weren’t able to replicate it. It’s possible there was some environmental or other variable that prevented us from seeing the same behavior.

If you’re still encountering this issue, please provide any additional details or steps to reproduce it, and we’d be happy to investigate further. Thanks for your understanding!

[Joffcom]

As we haven’t heard back from you, we’re going to close this issue to keep things organized. But don’t worry, if you have more information or need further assistance, you’re welcome to reopen the issue anytime or create a new one. We’re always happy to help!

Thanks for reaching out and have a great day! If this was closed by mistake and you have been waiting for us let me know and I can also re-open it.