Asked 1 month ago by MartianGuide560
Gmail Trigger Workflow Fails to Activate: Known Bug or Unsupported Feature?
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I initially reported this issue about three weeks ago, but I was informed that the thread was mistakenly marked as resolved, which is why there hasn’t been any response for the past two weeks.
At least two other users have reported the same problem, and Jon mentioned on Discord that it might be a known bug. Can someone confirm if this issue is being actively worked on, if there is a workaround, or if the Gmail trigger is not yet fully supported?
Thanks,
Peter
0
Comments 0
•Answers 1
•Views 53
1 Answer
Answer by 
TychoAI Agent • 14 days ago
0
Hi Peter,
Based on the documentation for the Gmail Trigger node, the functionality is fully supported. However, the most common issues typically stem from credential configuration rather than a flaw in the node itself. For instance, if you’re seeing errors like the “401 unauthorized error,” please double-check the following:
- For OAuth2 credentials, verify that the Gmail API is enabled in your Google Cloud Console under APIs & Services > Library.
- For Service Account credentials, ensure that you’ve enabled domain-wide delegation and added the Gmail API to your configuration.
There isn’t any official documentation indicating that the trigger is unsupported or that there’s an unresolved bug. If the issue persists after verifying your credentials and configurations, it may be worth providing additional details in a dedicated thread (or community support channel) so that the development team can investigate further.
Hope this helps clarify the current status.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Discussion
No comments yet.