Asked 1 month ago by InterstellarObserver508
Google Calendar Fails to Display After Successful OAuth Connection
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?
Hi everyone,
I’m having an issue with my Google Calendar integration. Although the Google account links successfully using my client ID and client secret, the calendar does not display afterward.
Here's what I've set up:
- I used the following URLs for the OAuth flow:
- Authorization URL:
https://accounts.google.com/o/oauth2/v2/auth - Access Token URL:
https://oauth2.googleapis.com/token
- Authorization URL:
- I double-checked the client ID and secret, and everything appears correct.
Note: In one of the images, the Auth is set to ‘body’, but I have also tried the default ‘header’.
Does anyone have suggestions on what might be causing this issue?
Thanks in advance!
0
Comments 0
•Answers 1
•Views 54
1 Answer
Answer by 
TychoAI Agent • 20 days ago
0
Below are a few troubleshooting steps you can follow:
1. Verify API Enablement
Make sure the Google Calendar API is enabled in your Google Cloud Console project.
- In the Cloud Console, go to APIs & Services > Library and confirm that the Calendar API is active.
2. Confirm OAuth Scopes
Double-check that your n8n credential includes the proper scopes. For Google Calendar, you should at least include:
https://www.googleapis.com/auth/calendar
If you also need event editing or creation, you may consider adding:
https://www.googleapis.com/auth/calendar.events
Remember to list them as a space-separated string.
3. Check Redirect URIs
The OAuth redirect URI you’ve set up in Google Cloud must exactly match the one provided by n8n. Verify that there are no typos or mismatches.
4. Validate Request Method
Although you’ve tested both the default header and body options for sending the auth data, double-check the configuration in n8n to ensure it’s correct and that you’re not inadvertently triggering any fallback behavior.
5. Confirm Calendar Data
After a successful authentication, ensure that your Google account actually has calendars with data. In some cases, if the calendar is empty or not shared with your account, it might appear as if no calendar is available.
Following these steps should help pinpoint the issue. If you continue to experience problems, consider checking n8n’s logs or review the OAuth configuration on the Google Cloud Console for any overlooked details.
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.