split out binary data
Configured with Form Trigger, Google Drive. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Files / media
- Routing
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| On form submission | Trigger | Form Trigger | See node parameters |
| Get Folder Name | Transform | Edit Fields | See node parameters |
| Search specific folder | Files / media | Google Drive | fileFolder |
| Folder found ? | Routing | If | See node parameters |
| Create Folder | Files / media | Google Drive | folder |
| Upload Files | Files / media | Google Drive | See node parameters |
| Prepare Files for Upload | Code | Code | See node parameters |
| Prepare Files for New Folder | Code | Code | See node parameters |
| Upload to New Folder | Files / media | Google Drive | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDriveOAuth2Api
Workflow notes
🗂️ Bulk File Upload to Google Drive with Folder Management
🗂️ Bulk File Upload to Google Drive with Folder Management
Overview
This workflow processes a form submission that accepts:
- Multiple file uploads (any format)
- Target folder name input
The workflow automatically:
- Checks if the specified folder exists in Google Drive
- Creates the folder if it doesn't exist
- Uploads all files to the correct folder
- Maintains original file names and structure
Perfect for batch uploading files while keeping your Drive organized!
🔄 Decision Point: Folder Check
🔄 Decision Point: Folder Check
The workflow splits into two paths based on folder existence:
- ✅ TRUE: Use existing folder path
- 🆕 FALSE: Create new folder path
🗂️ Existing Folder Path (Upper)
- Prepare Files for Upload: Splits files for individual processing
- Upload Files: Uploads to existing folder maintaining structure
📁 New Folder Path (Lower)
- Create Folder: Generates new folder in Drive
- Prepare Files for New Folder: Splits files for individual processing
- Upload to New Folder: Uploads to newly created folder
⚙️ File Processing Notes
⚙️ File Processing Notes
- All binary files are split individually for proper upload handling
- Original file names and structure are preserved
- Both paths ensure identical file organization
also see https://n8n.io/workflows/1621-split-out-binary-data/
🔍 Search Query Pattern
🔍 Search Query Pattern
The following search pattern looks for a folder with the specified name in a particular parent folder: Make sure to replace
mimeType='application/vnd.google-apps.folder' and name = '{{ $json.folderName }}' and '<folderId>' in parents
Important: Marl Always Output Data so you can check also if nothing found.
split out binary data
split out binary data
Purpose and structure
This folder contains the split out binary data workflow. Its executable nodes use code, formTrigger, googleDrive, if, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
On form submission
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Form/0733_Form_Code_Create_Triggered.json MIT; preserve source notices.