Block 1 - Get Existing Workflow Tags
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
Automatically deploy n8n workflows by simply dropping JSON files into a Google Drive folder—this template watches for new exports, cleans and imports them into your n8n instance, applies a tag, and...
n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.extractfromfile, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.googledrive, n8n-nodes-base.googledrivetrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jason Guest.
Original n8n.io sourceAutomatically deploy n8n workflows by simply dropping JSON files into a Google Drive folder—this template watches for new exports, cleans and imports them into your n8n instance, applies a tag, and then archives the processed files.
This workflow template is designed for n8n power users, and automation specialists who need a simple, reliable way to bulk‑deploy or version‑control n8n workflows via Google Drive. It’s perfect if you:
Manually importing .json exports into n8n is slow and error‑prone. With this template you can:
.json files executionOrder (and timezone if you choose) /api/v1/workflows 1. In Google Drive create a ToDeploy folder and a 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://SUBDOMAIN.YOURDOMAINNAME.com/api/v1/
4. Add n8n API authentication to:
5. Add your N8N instance URL to the N8N_Instance_URL variable in "Set n8n URL variable" node.
6. Run "1. Get Workflow Tags" flow and copy the ID of your chosen tag.
7. In "Set n8n API URL & Tag ID variables" node:
8. Set workflow to Active
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Deploy workflows from Google Drive to n8n instance |
|---|---|
| Complexity | advanced |
| Nodes | 21 |
| Categories | DevOps |
| Author | Jason Guest |
| Published | 16 Apr 2025 |
Use the JSON export at /data/workflows/3568/3568.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Automatically deploy n8n workflows by simply dropping JSON files into a Google Drive folder—this template watches for new exports, cleans and imports them into your n8n instance, applies a tag, and...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.