Skip to content

Trainer MVP: Course DB Builder

This workflow automates the process of building a course database by scanning Google Drive folders, extracting course materials, and structuring them for easy querying. It serves as the foundation for populating a trainer bot database with organized course content.

Purpose

No business context provided yet — add a context.md to enrich this documentation.

Based on the workflow implementation, this appears to be designed for: - Educational platforms or training organizations - Automated course content management - Building searchable course databases from Google Drive storage - Supporting AI-powered trainer bots with structured course data

How It Works

  1. Manual Trigger: An administrator manually starts the workflow
  2. Google Drive Connection: The workflow connects to Google Drive using OAuth2 credentials
  3. Folder Scanning: Retrieves the root folder structure from Google Drive
  4. Content Processing: (Implementation incomplete) Would process and structure course files
  5. Database Population: (Implementation incomplete) Would write structured data to a course database

Note: This workflow appears to be in early development with only the Google Drive connection implemented.

Mermaid Diagram

graph TD
    A[Manual Trigger] --> B[Google Drive - List Root Folder]
    B --> C[Process Course Content - Not Implemented]
    C --> D[Write to Database - Not Implemented]

    style C fill:#ffcccc
    style D fill:#ffcccc

Trigger

  • Type: Manual Trigger
  • Activation: Click "Test workflow" button in n8n interface
  • Use Case: On-demand execution when adding new courses or updating existing content

Nodes Used

Node Type Purpose Status
Manual Trigger Starts the workflow on demand ✅ Implemented
Google Drive Lists folders and files from Google Drive root ✅ Implemented
Sticky Notes Documentation and workflow description ✅ Implemented

External Services & Credentials Required

Google Drive API

  • Service: Google Drive API v3
  • Authentication: OAuth2
  • Credential Name: "Google Drive account"
  • Required Scopes:
    • https://www.googleapis.com/auth/drive.readonly (minimum)
    • https://www.googleapis.com/auth/drive (if file modifications needed)

Setup Requirements

  1. Google Cloud Console project with Drive API enabled
  2. OAuth2 credentials configured
  3. Appropriate permissions to access course folders

Environment Variables

No environment variables are currently used in this workflow. All configuration is handled through n8n credentials and node parameters.

Data Flow

Input

  • Trigger: Manual execution (no input data required)
  • Google Drive: Accesses root folder of connected Google Drive

Output

  • Current: List of folders and files from Google Drive root
  • Planned: Structured course data for database insertion

Data Structure

The Google Drive node currently returns standard Google Drive API responses containing: - File/folder IDs - Names and descriptions - MIME types - Creation/modification dates - Sharing permissions

Error Handling

No explicit error handling is currently implemented in this workflow. Consider adding: - Try-catch blocks around Google Drive operations - Validation for required folder structures - Fallback mechanisms for API rate limits - Logging for debugging failed operations

Known Limitations

  • Incomplete Implementation: Only Google Drive connection is functional
  • No Content Processing: Missing transcription and structuring logic
  • No Database Integration: Missing database write operations
  • Limited Error Handling: No robust error management
  • Single Drive Support: Only works with one Google Drive account
  • Manual Execution Only: No automated scheduling

No related workflows are documented. This appears to be a standalone component that would likely integrate with: - Course content delivery workflows - Trainer bot query systems - Content update notification systems

Setup Instructions

1. Import Workflow

  1. Copy the workflow JSON
  2. In n8n, go to Workflows → Import from JSON
  3. Paste the JSON and save

2. Configure Google Drive Credentials

  1. Go to Settings → Credentials
  2. Create new credential: "Google Drive OAuth2 API"
  3. Configure with your Google Cloud Console OAuth2 credentials:
    • Client ID
    • Client Secret
    • Redirect URL (from n8n)
  4. Complete OAuth2 flow to authorize access

3. Test Connection

  1. Open the workflow
  2. Click "Test workflow"
  3. Verify Google Drive node executes successfully
  4. Check that folder/file data is returned

4. Development Next Steps

To complete this workflow, you'll need to add: - Content processing nodes (for transcription/analysis) - Database connection nodes - Data transformation logic - Error handling mechanisms - Scheduling triggers (if automated execution desired)

5. Security Considerations

  • Ensure Google Drive credentials have minimal required permissions
  • Consider using service accounts for production deployments
  • Implement proper access controls for workflow execution
  • Regular credential rotation and monitoring