Why your n8n Gmail Trigger is not working (and how to fix it)
You connected Gmail. The node is green in the editor. Then production stays quiet—or every poll returns nothing—while new mail sits in the inbox. Searches for n8n gmail trigger not working usually surface docs and forum threads. Here is a single checklist aimed at self-hosted n8n. Scope of this article: documented against self-hosted n8n 2.44.6 . Not tested on n8n Cloud. Notification examples use…
The Gmail Trigger in n8n may not function properly due to several factors. First, ensure the workflow is published and active; drafts only remain in testing mode. Next, verify the self-hosted n8n has its own Google Cloud OAuth client with the Gmail API enabled and the correct redirect URI. This setup often breaks when the redirect URI is mismatched, the Gmail API is not enabled on the GCP project, or the app is in testing mode with an expired test-user grant.
Reconnecting the credential and confirming the same Google account owns the inbox can resolve this. The issue may also arise if the trigger is only tested in the editor with manual runs, which does not replicate the polling mechanism. Publish the workflow, wait for a full poll interval, and check the production Executions for activity.
Filters, such as search filters or label filters, could exclude messages from the trigger, resulting in zero items returned. Loosen the filters and confirm the test message is present in the primary inbox or the specified label. Additionally, if the poll interval is too sparse or Google returns errors like invalid_grant or quota issues, adjust the poll times or slow down the poll to avoid failures.
Finally, downstream nodes may fail, giving the appearance that the trigger is broken. Open the execution graph to identify any red nodes and resolve them individually rather than blaming the trigger itself.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
