Gmail Trigger now catches self-sent emails
The Gmail Trigger in n8n now correctly fires on self-sent emails that land in your inbox, closing a gap where messages sent to yourself were silently skipped.
The Gmail Trigger was dropping self-sent emails without warning. Users relying on common patterns—contact forms that email themselves, or developers testing workflows by sending a message to their own address—found their workflows simply wouldn't fire. Gmail itself displays these messages in the inbox, but n8n was ignoring them.
A simple fix to the label-checking logic now allows the trigger to process messages that carry both SENT and INBOX labels. Outgoing-only messages (those with SENT but no INBOX) remain excluded, so purely sent mail still won't spur workflows. The change affects the Gmail Trigger node in the n8n nodes-base package and resolves issue #19302.
View Original GitHub Description
Summary
Problem:
Self-sent emails (e.g., abc@gmail.com → abc@gmail.com) were being skipped by the Gmail Trigger
because the logic ignored all messages with the SENT label. This caused workflows not to run
when sending emails to yourself, which is a common scenario for testing or contact forms.
Solution:
Now, emails are only skipped if they have the SENT label and are not in the INBOX.
This ensures self-sent emails that appear in the inbox still trigger workflows, while purely
outgoing messages remain ignored.
Testing:
- Connect Gmail Trigger to an account.
- Send an email to yourself.
- Verify the workflow triggers correctly.
Related Linear tickets, Github issues, and Community forum posts
- Fixes #19302
- https://linear.app/n8n/issue/NODE-3610/community-issue-gmail-trigger-doesnt-run-on-messages-sent-to-self
- https://linear.app/n8n/issue/NODE-3632/community-pr-fixgmail-trigger-handle-self-sent-emails-in-inbox
Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
release/backport(if the PR is an urgent fix that needs to be backported)