Gmail trigger
Hi all,
Since this week I'm having problem with a gmail trigger, it's not activating. I received an new email, I see it on my inbox, but the trigger do nothing. On the logs only shows that last time it works (2025-08-17).
I use other gmail nodes (send email) and that is still working, so I can rule out a problem with my credentials. I Already delete the trigger, add it again.
When a try the gmail trigger and click on "Get data" I got the following response "No data found. Send a request to the API and try again."
2 Replies
Processing...
🤖 Compiling the latest insights for you. 🔄 this might take a couple of minutes... beep boop
🤖 AI Response
Based on recent reports, issues with the Gmail trigger not activating are common and can be caused by several factors, including API permission problems, workflow configuration errors, or platform-specific bugs. Users have noted that the trigger may work inconsistently—sometimes only firing 40–50% of the time, or stopping entirely after a few hours or days, even when emails are received as expected. In some cases, the trigger works in manual tests but fails during automated or scheduled runs.
Key troubleshooting steps include:
- Rechecking trigger configuration and permissions: Ensure the Gmail trigger is set up with the correct scope and that your Gmail account is properly authorized.
- Recreating the trigger node: Sometimes deleting and recreating the trigger with fresh authentication can resolve connection issues.
- Adjusting polling intervals: Reducing the polling interval in the trigger settings may help avoid hitting API limits or timeouts.
- Monitoring the correct folder: Double-check that the trigger is set to monitor the intended folder (e.g., inbox vs. other folders).
- Restarting or reactivating workflows: Stopping and reactivating the workflow has resolved the issue for some users.
- Checking for platform outages or bugs: Some outages (e.g., GCP outages) or recent updates may temporarily affect trigger reliability.
If these steps do not resolve the issue, it is recommended to contact in-app support for further investigation, as the problem may be related to specific workflow configurations or recent platform changes.
🔗 References:
1. https://support.buildship.com/m/1383019233247756298
2. https://community.activepieces.com/t/gmail-trigger-new-email-not-triggering/6413
3. https://community.n8n.io/t/gmail-trigger-not-triggering-after-a-couple-of-hours/137997
4. https://pipedream.com/community/t/why-is-the-new-email-received-trigger-in-gmail-not-working-despite-no-error-messages-in-the-logs/11533
5. https://github.com/n8n-io/n8n/issues/10098
BuildShip AI Support