Drop a JSON file into a Google Drive folder and it becomes a live n8n workflow with the right tag applied. This is useful for teams that want a simple release pipeline for n8n without logging into the editor for every import.

A Google Drive event starts the run, downloads the file, and pulls out the JSON. Clean code then strips unsupported fields so the import will not fail. The system sets your n8n URL and tag values, creates the workflow through the n8n API, and assigns the tag. If creation fails, the name is captured for quick review. The file is moved to a Deployed folder so you know it is done.

Setup needs a Google Drive account and an n8n API key. Expect faster releases, fewer mistakes, and clear status by folder. Common uses include shipping new automations from a shared Drive, tagging them by team or environment, and keeping a simple audit trail with the moved files.

• Google Drive event trigger watches a ToDeploy folder and starts the run when a JSON file appears.
• File download pulls the JSON file directly from Drive for processing.
• JSON extraction reads the file and prepares the data for import.
• Cleanup code removes unsupported fields so the n8n API accepts the payload.
• HTTP calls create the workflow in your n8n instance using your API key.
• Tag assignment applies a chosen tag to keep new workflows organized.
• Error capture stores the workflow name when creation fails to speed up fixes.
• File move sends the processed JSON to a Deployed folder to show it is complete.
• Manual test path lets you fetch tag IDs and verify settings before going live.

• Reduce manual imports from 30 minutes to 2 minutes per workflow by using Drive uploads
• Eliminate up to 90% of copy paste errors with automatic JSON cleanup
• Streamline release steps by 70% with a single folder drop
• Handle dozens of workflow files in one day without extra staff
• Connect Google Drive and n8n so creators and operators work in one simple flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Drive and n8n. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a Google Drive credential. Double click the Google Drive Trigger node and the Download and Move file nodes, choose the credential dropdown, click Create new credential, then follow the on screen steps to connect your Google account.
4. Set the Google Drive Trigger to your ToDeploy folder. In the Move file node, choose your Deployed folder as the destination.
5. Create an n8n API key in your n8n settings. Copy the key and your base URL, for example https://yourdomain.com/api/v1/.
6. In the n8n credentials manager, create an n8n API credential. Double click the Get Existing Workflow Tags, Create Workflow, and Set Workflow Tag nodes, choose the credential dropdown, click Create new credential, paste your API key, and set the base URL.
7. Open the Set n8n URL variable and Set n8n API URL and Tag ID variables nodes. Enter your n8n instance URL and paste the tag ID once you have it.
8. Run the Get Existing Workflow Tags node once to list tag IDs. Copy the ID for the tag you want to use.
9. Click the manual trigger to test the path and confirm credentials work. Check that you can fetch tags without errors.
10. Drop a sample workflow JSON into the ToDeploy folder. Confirm a new workflow appears in n8n, the tag is applied, and the file moves to the Deployed folder.
11. If you see 401 errors, verify the API key and base URL. If imports fail, review the Capture Name node output and confirm the JSON file is a valid n8n export.
12. Activate the workflow when tests pass so Drive uploads deploy new workflows automatically.