How can I fix the OAuth Redirect URL space issue in Google Calendar integration?

Below is some guidance to resolve the issue:

What’s Happening?

The 400 Bad Request error is occurring because the predetermined OAuth Redirect URI provided by n8n for your Google Calendar node contains a space. Google’s Authorized Redirect URIs cannot include any whitespace. The error message you received looks similar to:

PLAINTEXTCopied
400 Bad Request

It indicates that the redirect URI doesn't meet Google's formatting requirements.

What to Do?

1. Remove the Space
   Edit the redirect URI so that it doesn't include any space. If the space is coming from extra whitespace in the URL, remove it manually before adding it as an Authorized Redirect URI in the Google Cloud Console.

2. Update Google Cloud Console
   Once you have the correct redirect URI (without spaces), update your Google Cloud Console OAuth credentials by replacing the existing redirect URI with the corrected version.

3. Recreate or Test Credentials
   After updating, try to sign in again with your Google Calendar credentials in n8n. This should resolve the 400 Bad Request error.

Additional Information

• Double-check that your OAuth Redirect URI exactly matches what n8n specifies (minus the unwanted space).
• If you're using n8n Cloud or a self-hosted instance, ensure that any modifications you make in your credential settings are saved properly.

---

Since you're sharing the details typically included in a workflow and setup info, please make sure that any workflow or system details you share do not include sensitive information.

If you have further questions specifically about Google Calendar node credentials or any issues with OAuth credential setup in n8n, please share the exact error message (if it differs) or let me know what part of the process is still unclear.