Automated Workflow Metadata Generation to Google Drive
detail.loadingPreview
This workflow automatically retrieves a list of n8n workflows, fetches details for each, merges them, and uploads the structured metadata as JSON files to Google Drive daily.
About This Workflow
This workflow automates the process of extracting metadata from your n8n instance and storing it in Google Drive. It's designed to run daily, ensuring you have an up-to-date backup or record of your workflow configurations. The process involves fetching a list of all workflows, then iteratively retrieving details for each workflow, merging this data, converting it into a binary JSON format, and finally uploading it to a specified Google Drive folder.
Key Features
- Scheduled Execution: Runs automatically daily at 2:30 AM.
- n8n API Integration: Uses HTTP requests to interact with the n8n REST API to fetch workflow data.
- Data Merging: Combines workflow list data with individual workflow details.
- JSON to Binary Conversion: Prepares the structured data for efficient storage.
- Google Drive Integration: Uploads the generated JSON files to a designated Google Drive folder.
- Configurable Output: The filename and target folder in Google Drive can be customized.
How To Use
- Trigger: The workflow can be manually triggered by clicking 'execute' or automatically started by the 'Run Daily at 2:30am' cron trigger.
- Get Workflow List: The
Get Workflow Listnode fetches all workflows from your n8n instance via the/rest/workflowsendpoint. Ensure yourn8n Credsare correctly set up for basic authentication. - Map: The
Mapnode processes the list of workflows, preparing them for the next stage. - Get Workflow: The
Get Workflownode is called for each workflow ID obtained from theMapnode, fetching the detailed configuration of that specific workflow. This node also requires then8n Creds. - Merge: The
Mergenode combines the data from the workflow list and the individual workflow details. It usesmergeByIndexto align the data correctly. - FunctionItem: The
FunctionItemnode restructures the merged data, making it ready for conversion. - Move Binary Data: This node converts the structured JSON data into a binary format suitable for upload.
- Google Drive: The
Google Drivenode uploads the binary JSON file to your Google Drive.- Filename: The filename is dynamically set using the workflow's
nameproperty (e.g.,{{$node["Merge"].data["name"]}}.json). - Folder ID: You must replace the placeholder text in the
parentsfield with the actual ID of your desired Google Drive folder. This ID can be found in the URL when you navigate to the folder in Google Drive. - Credentials: Ensure your
testGoogle Cloud credentials are correctly configured.
- Filename: The filename is dynamically set using the workflow's
Apps Used
Workflow JSON
{
"id": "36f73250-f39b-4920-ad86-6074517f5523",
"name": "Automated Workflow Metadata Generation to Google Drive",
"nodes": 21,
"category": "Data Management",
"status": "active",
"version": "1.0.0"
}Note: This is a sample preview. The full workflow JSON contains node configurations, credentials placeholders, and execution logic.
Get This Workflow
ID: 36f73250-f39b...
About the Author
N8N_Community_Pick
Curator
Hand-picked high quality workflows from the global community.
Statistics
Related Workflows
Discover more workflows you might like
Sync Google Drive Files with OpenAI Vector Store
Automatically syncs files from Google Drive to an OpenAI vector store, ensuring up-to-date embeddings for AI applications.
FileMaker Data Entry and Update
Workflow to create a record in FileMaker, then edit it with additional data.
Dynamically Create Airtable Tables for Webflow Form Submissions
Automatically create dedicated Airtable tables for each Webflow form and log submissions.