Skip to main content

Deploy workflows from Google Drive to n8n instance

Workflow preview

Workflow preview
100%
Deploy workflows from Google Drive to n8n instance preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

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

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jason Guest.

Original n8n.io source

1.1 Workflow description

Title
Deploy workflows from Google Drive to n8n instance
Workflow name
Deploy workflows from Google Drive to n8n instance

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 then archives the processed files.

Who is this template for?

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:

  • Manage multiple n8n instances (staging, production, etc.)
  • Want an easy “drop‑in” approach to publish new or updated workflows
  • Prefer storing/exporting JSON in Drive rather than editing in the UI

Use case

Manually importing .json exports into n8n is slow and error‑prone. With this template you can:

  • Keep your workflows in a shared Drive folder (version control friendly)
  • Automatically sanitize each file so only supported settings go through
  • Tag deployed workflows consistently for easy filtering
  • Move processed files to a “Deployed” folder for clear change tracking

How it works

  1. Watch “ToDeploy” folder in Google Drive for new .json files
  2. Download & parse each file into a JSON object
  3. Clean payload: strip out everything except the allowed executionOrder (and timezone if you choose)
  4. POST the cleaned workflow to your n8n instance via /api/v1/workflows
  5. PUT a predefined tag onto the newly created workflow
  6. Move file to your “Deployed” folder when import succeeds, or capture the workflow name & error if it fails

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://SUBDOMAIN.YOURDOMAINNAME.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 "1. Get Workflow Tags" flow 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

8. Set workflow to Active


How to adjust it to your needs

  • Use different tags: run Get Existing Workflow Tags on start‑up to refresh available tags, or hard‑code multiple tags in the Set Workflow Tag node.
  • Add notifications: connect the error branch to Slack or Email nodes so you get alerted if an import fails.
  • Swap Drive for another storage: replace Google Drive nodes with Dropbox, S3, or GitHub triggers if you prefer a different source for your JSON files.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Get Existing Workflow Tags

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 2 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 7 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Extract JSON object from File

Type / Role
n8n-nodes-base.extractFromFile - extractFromFile
Config choices
Version 1

Block 9 - Clean JSON file ready for import

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 10 - Set n8n API URL & Tag ID variables

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 11 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Create n8n Workflow

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 14 - Set Workflow Tag

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 15 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Capture Name If Fails To Create Workflow

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 17 - Move JSON file to Deployed folder

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 18 - Download n8n JSON File

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 19 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Set n8n URL variable

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 21 - Google Drive Trigger -ToDeploy folder

Type / Role
n8n-nodes-base.googleDriveTrigger - googleDriveTrigger
Config choices
Version 1

3. Summary Table

Workflow Deploy workflows from Google Drive to n8n instance
Complexity advanced
Nodes 21
Categories DevOps
Author Jason Guest
Published 16 Apr 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3568/3568.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Deploy workflows from Google Drive to n8n instance do?

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...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.