Why your n8n Gmail Trigger is not working (and how to fix it)

Description and use

The Gmail Trigger issue in self‑hosted n8n is resolved by ensuring the workflow is published, OAuth is correctly configured, filters are appropriate, poll intervals are set, and downstream nodes are functioning.

Problem

The Gmail Trigger node in self‑hosted n8n remains silent, returning no messages even though new mail arrives in the inbox.

Outcome

After following the checklist, the Gmail Trigger polls successfully, returning new messages and triggering downstream actions.

Workflow

• Publish and activate the workflow
• Verify OAuth credentials and Gmail API enablement
• Confirm redirect URI matches exactly
• Ensure the same Google account owns the inbox
• Run a manual test to confirm trigger path
• Loosen search/label filters temporarily
• Check poll interval and rate limits
• Inspect execution logs for failures
• Fix any downstream node errors (Slack, labels, LLM)
• Add a content‑presence gate if needed
• Test with a real email in production mode

Evidence

The Gmail Trigger polls Gmail on an interval (often about every minute by default, depending on your Poll Times). Each successful poll should only return new messages that match your filters.

Source

Triggers that poll on a schedule need a published workflow. Draft-only saves do not keep listening in production.

Source

Self-hosted n8n needs your own Google Cloud OAuth client with the Gmail API enabled, redirect URI copied from the n8n credential dialog, and a completed Sign in with Google.

Source

Clicking Execute workflow can exercise downstream nodes with pinned or sample data without proving the trigger poll path.

Source

Search filters, label filters, “unread only,” spam/trash exclusions, or a filter aimed at the wrong mailbox will yield successful polls with zero items.

Source