n8n workflow deployer
Configured with Extract From File, Google Drive, Google Drive Trigger, HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Trigger
- Transform
- Code
- Files / media
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 |
|---|---|---|---|
| Get Existing Workflow Tags | Web / API | HTTP Request | See node parameters |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Extract JSON object from File | Transform | Extract From File | fromJson |
| Clean JSON file ready for import | Code | Code | See node parameters |
| Set n8n API URL & Tag ID variables | Transform | Edit Fields | See node parameters |
| Create n8n Workflow | Web / API | HTTP Request | POST |
| Set Workflow Tag | Web / API | HTTP Request | PUT |
| Capture Name If Fails To Create Workflow | Code | Code | See node parameters |
| Move JSON file to Deployed folder | Files / media | Google Drive | move |
| Download n8n JSON File | Files / media | Google Drive | download |
| Set n8n URL variable | Transform | Edit Fields | See node parameters |
| Google Drive Trigger -ToDeploy folder | Trigger | Google Drive Trigger | 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
googleDriveOAuth2Apin8nApi
Workflow notes
Setup Instructions
Setup Instructions
1. In Google Drive create a ToDeploy folder and a Deployed folder
- Update "Google Drive Trigger -ToDeploy folder" to your ToDeploy folder
- Update "Move JSON file to Deployed folder" to you Deployed folder
2. Create a n8n API key: +Go to Settings > n8n API +Select Create an API key +Copy API Key
3. In "Get Existing Workflow Tags" node: Create n8n API Authentication Authentication: Predefined Credential Type Credential Type: n8n API
Create new credential: +Paste in API key +Baseurl: https://SUB.DOMAINNAME.com/api/v1/
4. Add n8n API authentication to:
- "Create n8n Workflow" node
- "Set Workflow Tag" node
5. Add your N8N instance URL to the N8N_Instance_URL variable in "Set n8n URL variable" node.
6. Run "Get Workflow Tags" node and copy the ID of your chosen tag.
7. In "Set n8n API URL & Tag ID variables" node:
- Add the Workflow Tag ID to the N8N_Instance_Tag variable
- Add your N8N instance URL to the N8N_Instance_URL variable
9. Set workflow to Active
10. Add n8n json files to Google Drive folder
Set variables:
Set variables:
N8N_Instance_Tag N8N_Instance_URL
Set variable:
Set variable:
N8N_Instance_URL
Configure n8n API authentication.
Configure n8n API authentication.
Tag ID
Copy your chosen Tag ID to N8N_Instance_Tag
n8n workflow deployer
n8n workflow deployer
Purpose and structure
This folder contains the n8n workflow deployer workflow. Its executable nodes use code, extractFromFile, googleDrive, googleDriveTrigger, httpRequest, manualTrigger, 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
When clicking ‘Test workflow’, Google Drive Trigger -ToDeploy folder
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/Code/1814_Code_Extractfromfile_Automate_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Configure n8n API authentication
- 1. Get Workflow Tags
- Change Google Drive Folder
- Change Google Drive Deployed Folder
- 2. Import JSON Workflow Into n8n Instance