Trainer MVP: Course DB Builder¶
This workflow automates the process of scanning Google Drive folders to build a structured database of course content, with the goal of transcribing audio files and organizing them for easy querying and retrieval.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
Based on the workflow description, this system is designed to help trainers and educators organize their course materials by automatically processing Google Drive folders containing audio content. The workflow aims to transcribe voice recordings and structure them in a database format that enables efficient searching and content retrieval for course development and delivery.
How It Works¶
Currently, this workflow is in its initial development stage with only the foundation implemented:
- Manual Trigger: The workflow starts when a user manually clicks "Test workflow"
- Google Drive Scan: Connects to Google Drive and lists all folders in the root directory
- Future Processing: The workflow is designed to eventually process audio files within these folders, transcribe them, and store the structured data in a database
Note: This workflow appears to be incomplete and requires additional nodes to fulfill its stated purpose of transcription and database building.
Mermaid Diagram¶
graph TD
A[Manual Trigger] --> B[Google Drive - List Folders]
style A fill:#e1f5fe
style B fill:#f3e5f5
Trigger¶
- Type: Manual Trigger
- Activation: User clicks "Test workflow" button
- Frequency: On-demand execution only
Nodes Used¶
| Node Type | Purpose | Configuration |
|---|---|---|
| Manual Trigger | Initiates the workflow manually | Default settings |
| Google Drive | Lists folders in Google Drive root directory | Connected to "My Drive", scanning root folder |
| Sticky Note | Documentation of workflow purpose | Contains workflow description |
External Services & Credentials Required¶
Google Drive¶
- Service: Google Drive API
- Credential Type: OAuth2
- Required Permissions:
- Read access to Google Drive folders
- File listing capabilities
- Setup: Configure "Google Drive account" OAuth2 credentials in n8n
Environment Variables¶
No environment variables are currently configured for this workflow.
Data Flow¶
Input¶
- Trigger: Manual user action
- Source Data: Google Drive folder structure
Output¶
- Current: List of folders from Google Drive root directory
- Planned: Transcribed audio content structured for database storage
Data Structure¶
The Google Drive node outputs folder information including: - Folder names - Folder IDs - Metadata (creation dates, permissions, etc.)
Error Handling¶
No explicit error handling is currently implemented in this workflow. Consider adding error handling for: - Google Drive API connection failures - Authentication issues - Rate limiting scenarios
Known Limitations¶
- Incomplete Implementation: The workflow only lists folders but doesn't process audio files or perform transcription
- No Database Integration: Missing nodes for database storage and querying
- No Audio Processing: Lacks transcription capabilities mentioned in the purpose
- Manual Execution Only: No automated scheduling or event-based triggers
Related Workflows¶
No related workflows identified in the current context.
Setup Instructions¶
Prerequisites¶
- n8n instance with Google Drive integration enabled
- Google account with access to the target Drive folders
- Appropriate Google Drive API permissions
Installation Steps¶
-
Import Workflow
1# Import the workflow JSON into your n8n instance -
Configure Google Drive Credentials
- Go to n8n Credentials section
- Create new "Google Drive OAuth2 API" credential
- Follow OAuth2 setup process with Google
- Name the credential "Google Drive account"
-
Test Connection
- Open the workflow in n8n editor
- Click "Test workflow" to verify Google Drive connection
- Confirm that folders are listed successfully
-
Future Development
- Add audio file processing nodes
- Implement transcription service integration
- Configure database storage nodes
- Add error handling and logging
Verification¶
After setup, the workflow should successfully connect to Google Drive and return a list of folders from the root directory. This confirms the foundation is working and ready for additional development to complete the transcription and database building functionality.