Chapter 5: n8n Cloud vs. Lab Playground Differences (API/Google Auth Setup)¶

Video: Watch this chapter on YouTube (45:06)

Overview¶

This chapter explains the key differences between using n8n Cloud and the CodeCloud lab playgrounds. It covers the specific configurations needed for each environment, particularly focusing on API key setup with CodeKey and Google OAuth authentication for services like Gmail.

Detailed Summary¶

Initial Lab Setup¶

When entering a lab environment for the first time:

1. Enter credentials: Email, first name, last name, and password
2. These are NOT saved anywhere permanent
3. You can use different credentials for each lab instance
4. Skip onboarding: Hit "Get Started" to bypass questionnaires
5. Skip paid features: Click "Skip" for paid feature prompts
6. Access dashboard: Similar to n8n Cloud environment

Building the Email AI Agent in Labs¶

Starting the Workflow¶

1. Click "Start from scratch"
2. Add a Chat Trigger node
3. Add an AI Agent node
4. Select OpenAI Chat Model

Using CodeCloud Keyspace in Labs¶

Finding CodeKey Access¶

1. Look at the left-hand instruction panel in the lab
2. Click the CodeKey link provided
3. Hit "Launch Now"
4. Click "Start Playground"

Configuring CodeKey Credentials¶

1. Select the desired model (e.g., OpenAI GPT-4.1)
2. Copy the API Key
3. In n8n, create new credential
4. Paste the API Key
5. Important: Replace the base URL with CodeKey's base URL
6. Click Save

Expected result: "Connection tested successfully"

The Model Selection Issue¶

When using CodeKey, the model dropdown won't work correctly:

Problem: - "Pick from list" shows incorrect/incompatible models - Selecting from list causes errors

Solution: 1. Change to "By ID" 2. Copy exact model name from lab instructions: openai/gpt-4.1 3. Paste word-for-word

Using OpenAI API Keys Directly¶

For comparison, using native OpenAI keys is more straightforward:

Getting OpenAI API Key¶

1. Go to platform.openai.com
2. Navigate to API Keys section
3. Click "Create new secret key"
4. Name it (e.g., "email integration")
5. Copy the API key

Configuring in n8n¶

1. Create new credential
2. Name it (e.g., "OpenAI Account 2")
3. Paste API key
4. Leave base URL as default (don't modify)
5. Click Save

Advantage: Model dropdown works correctly—you can pick from list normally.

Google OAuth Setup for Gmail (Lab Environment)¶

The major difference between n8n Cloud and labs is Google authentication:

n8n Cloud (Easy Method)¶

• "Sign in with Google" button available
• One-click OAuth if using Chrome browser

Lab Environment (Manual OAuth)¶

Requires manual Google Cloud Console setup:

Step-by-Step Google OAuth Configuration¶

Step 1: Create Google Cloud Project¶

1. Go to console.cloud.google.com
2. Click on project selector (top left)
3. Click "New Project"
4. Name it (e.g., "n8n Email App")
5. Select "No organization"
6. Click "Create"
7. Select the new project

Step 2: Enable Gmail API¶

1. Search for "Gmail API"
2. Click on Gmail API
3. Click "Enable"

Step 3: Configure OAuth Consent Screen¶

1. Navigate to "OAuth consent screen"
2. Click "Get Started"
3. Enter App Information:
4. App name: "n8n Email App"
5. User support email: Your email
6. Select "External" for audience
7. Add contact information email
8. Click Continue → Create

Step 4: Add Test Users¶

1. Go to "Audience" section
2. Add a test user (email you'll use for sending)
3. Save

Step 5: Create OAuth Client ID¶

1. Go to "API and Services" → "Credentials"
2. Click "Create Credentials" → "OAuth client ID"
3. Application type: "Web application"
4. Name it (e.g., "n8n Email OAuth Client")
5. Add Authorized Redirect URI:
6. Copy from n8n credential setup screen
7. Paste into Google Cloud Console
8. Click "Create"

Step 6: Copy Credentials to n8n¶

1. Copy Client ID from Google
2. Paste into n8n Client ID field
3. Copy Client Secret from Google
4. Paste into n8n Client Secret field
5. "Sign in with Google" button now appears!

Step 7: Complete OAuth Flow¶

1. Click "Sign in with Google"
2. Select your Google account
3. See "Google hasn't verified this app" warning
4. Click "Continue" (you created it, so it's safe)
5. Select all permissions
6. Click "Continue"
7. See "Connection successful"

Testing the Gmail Integration¶

After setup: 1. Configure Gmail node for sending 2. Set fields to "Determine by model" 3. Test with a message: "Hi, can you send an email to [email] to just say hello" 4. Workflow sends email successfully

Key Differences Summary¶

Troubleshooting Notes¶

If experiencing issues during builds, consider:

1. Self-hosted vs Cloud differences: Some features are Cloud-only
2. Version variations: Labs may run different n8n versions
3. Community nodes: Availability may differ
4. Workarounds exist: Most limitations have alternative solutions

Applying to Other Google Services¶

The same OAuth setup applies to: - Google Sheets - Google Drive - Google Docs - Other Google APIs

For each service: 1. Enable the specific API in Google Cloud Console 2. Use the same OAuth credentials 3. API must be enabled before use

Key Takeaways¶

1. Lab credentials are temporary: You don't need to remember passwords used in lab environments.

2. CodeKey requires "By ID" selection: Always type the exact model name rather than selecting from dropdown.

3. OpenAI direct keys work normally: Native OpenAI API keys allow normal model selection from lists.

4. Google OAuth differs by environment: n8n Cloud has one-click; labs require manual Google Cloud setup.

5. OAuth consent screen is required: Google requires app registration before OAuth access.

6. Test users must be added: For "External" apps, add your email as a test user.

7. Same OAuth works for all Google services: One setup enables Gmail, Sheets, Drive, and Docs.

8. Enable APIs individually: Each Google API must be explicitly enabled in Cloud Console.

9. Redirect URIs must match: Copy exact URI from n8n into Google Cloud Console.

10. Workarounds exist: Lab limitations don't prevent learning—alternative approaches are available.

Conclusion¶

Understanding the differences between n8n Cloud and lab environments prevents frustration during hands-on exercises. While n8n Cloud offers streamlined authentication with services like Google, the lab environment provides valuable experience with manual OAuth configuration—a skill needed for self-hosted deployments. The CodeKey integration works similarly in both environments but requires specific model naming conventions. By mastering both approaches, learners gain flexibility to work in any n8n environment, whether cloud-hosted, self-hosted, or in educational lab settings. This knowledge is particularly valuable for enterprise deployments where manual OAuth configuration is often required for security compliance.