n8n Workflow Deployer

n8n Workflow Deployer Core Function & Value This workflow automates the deployment of new n8n workflows into an n8n instance directly from Google Drive. It functions as a simple Continuous Integration/Continuous Deployment (CI/CD) pipeline for n8n workflows. By dropping a workflow's JSON file into a designated "ToDeploy" folder in Google Drive, this system automatically imports it, cleans it for compatibility, assigns a predefined tag, and then moves the file to a "Deployed" folder for archival. This automation provides significant value by streamlining the process of adding new workflows, ensuring consistency through automatic tagging, and creating an organized backup system in Google Drive. It eliminates the manual steps of exporting/importing JSON and is ideal for teams sharing workflows or for developers managing deployments across different n8n environments. Technologies Used - Google Drive: Used as the trigger source and for file storage, acting as a repository for workflows to be deployed and those that have been deployed. - n8n API: The workflow heavily uses the native n8n API to programmatically create new workflows and manage their tags within the instance. - HTTP Requests: Core to the interaction with the n8n API. Node-by-Node Analysis The workflow is functionally divided into two parts: a one-time manual setup and the primary automated deployment trigger. H3 Manual Setup Path This part of the flow is run once to retrieve necessary information, like the ID for a workflow tag. - When clicking ‘Test workflow’ (Manual Trigger): A manual starting point for the user to run the setup process. - Set n8n URL variable: Sets a variable containing the base URL of the user's n8n instance. This is required to build the correct API endpoints. - Get Existing Workflow Tags (HTTP Request): Makes a GET request to the n8n API endpoint /api/v1/tags. Its purpose is to fetch a list of all existing workflow tags in the instance. The user can then inspect this output to find the unique id of the tag they wish to apply to all future deployed workflows.