How Do I Retrieve the Google OAuth Redirect URL on n8n Cloud?

Below is how you can get and use the OAuth redirect URL when using n8n Cloud:

Locate the OAuth Redirect URL in n8n

When you create or edit your Google OAuth credentials in n8n (whether for a single service or generic OAuth2), you’ll see a field labeled similar to OAuth Redirect URL. This URL is generated automatically by n8n Cloud. Here's what you need to do:

1. Open your n8n instance (via your n8n Cloud dashboard).
2. Navigate to your credentials settings where you’ve created your Google OAuth credential.
3. Copy the OAuth Redirect URL that’s provided. This URL is what n8n will use to complete the OAuth flow once Google returns the authentication code.

Configure Google Cloud Console

After copying the OAuth Redirect URL from n8n, you need to add it to your Google Cloud Console configuration:

1. Open the Google Cloud Console.
2. Open your project and navigate to APIs & Services > Credentials.
3. Select + CREATE CREDENTIALS > OAuth client ID (or edit your existing OAuth client).
4. In the Authorized redirect URIs section, paste the OAuth Redirect URL you copied from n8n.
5. Save your changes.

This ensures that when you click Sign in with Google in n8n, Google knows to redirect back to your n8n environment.

Troubleshooting Tips

• Double-check the URL: Make sure there are no extra spaces or typos when pasting the URL into Google Cloud.
• Confirm n8n Cloud Domain: Since you’re using n8n Cloud, ensure that the domain in the redirect URL (e.g. something like n8n.cloud) exactly matches what you have set up in your Google Cloud Console’s Authorized Domains.
• Refresh Credentials: If you update the redirect URL in Google Cloud Console, try re-initiating the OAuth flow in n8n to ensure the changes take effect.

By following these steps, you should be able to successfully configure the OAuth flow, allowing you to authenticate with Google. If you still encounter issues, check the n8n documentation for Google OAuth credentials and ensure that all steps (like enabling APIs and configuring the OAuth consent screen) have been completed.