Create workflow inventory dashboard with n8n API and Google Sheets
This workflow provides a powerful way to automatically document and maintain an inventory of all your n8n workflows in a Google Sheet. By running on a schedule or manually, it fetches details about every workflow on your instance, processes the key information, and then populates a spreadsheet. This creates a centralized, up-to-date dashboard for auditing, monitoring, and understanding your automation landscape.
Who is this for?
This workflow is ideal for n8n administrators, developers, and teams who manage multiple workflows. If you need a clear and simple way to track all your automations, their components, and their statuses without manually checking each one, this template is for you. It's particularly useful for maintaining technical documentation, auditing node usage across your instance, and quickly finding specific workflows.
What problem is this workflow solving?
As the number of workflows on an n8n instance grows, it becomes challenging to keep track of them all. Questions like "Which workflows use the HubSpot node?", "Which workflows are inactive?", or "When was this workflow last updated?" become difficult to answer. This workflow solves that problem by creating a single source of truth in a Google Sheet. It automates the process of cataloging your workflows, saving you time and ensuring your documentation is always current.
What this workflow does
- Triggers Execution: The workflow can be initiated either on a set schedule (via the Scheduled Start node) or manually (via the Manual Start node).
- Fetches All Workflows: The
Get All Workflowsnode connects to your n8n instance via the API to retrieve a complete list of your workflows and their associated data. - Processes Workflows Individually: The
Loop Through Each Workflownode iterates through each retrieved workflow one by one so they can be processed individually. - Extracts Key Information: The
Extract Workflow Detailsnode uses custom code to process the data for each workflow, extracting essential details like its name, ID, tags, and a unique list of all node types it contains. - Updates Google Sheet: The
Add/Update Row in Google Sheetnode then takes this information and appends or updates a row in your designated spreadsheet, using the workflow ID as a unique key to prevent duplicates. - Waits and Repeats: The
Pause to Avoid Rate Limitsnode adds a short delay to prevent issues with API limits before the loop continues to the next workflow.
Setup
-
Configure
Get All WorkflowsNode:- Select the
Get All Workflowsnode. - In the 'Credentials' section, provide your n8n API credentials to allow the workflow to access your instance's data.
- Select the
-
Prepare Your Google Sheet:
- Create a new Google Sheet.
- Set up the following headers in the first row:
id,title,link,tags,nodes,CreatedAt,UpdatedAt,Active,Archived.
-
Configure
Add/Update Row in Google SheetNode:- Select the
Add/Update Row in Google Sheetnode. - Authenticate your Google account in the 'Credentials' section.
- In the 'Document ID' field, enter the ID of your Google Sheet. You can find this in the sheet's URL (e.g.,
.../spreadsheets/d/THIS_IS_THE_ID/edit). - Select your sheet from the 'Sheet Name' dropdown.
- Under 'Columns', ensure the
idfield is set as the 'Matching Columns' value. This is crucial for updating existing rows correctly.
- Select the
-
Activate the Workflow:
- Choose your preferred trigger. You can enable the
Schedule Triggerto run the sync automatically at regular intervals. - Save and activate the workflow.
- Choose your preferred trigger. You can enable the
How to customize this workflow to your needs
- Track Different Data: You can modify the
Extract Workflow Detailsnode to extract other pieces of information from the workflow JSON. For example, you could parse thesettingsobject or count the total number of nodes. Remember to add a corresponding column in your Google Sheet and map it in theGoogle Sheetsnode. - Add Notifications: Add a notification node (like Slack, Discord, or Email) after the
Loop Through Each Workflownode (in the second output) to be alerted when the sync is complete or if an error occurs. - Filter Workflows: You can add an
IFnode after theLoop Through Each Workflownode to filter which workflows get added to the sheet. For instance, you could choose to only log active workflows ({{ $('Loop Through Each Workflow').item.json.active }}is true) or workflows containing a specific tag. - Adjust Wait Time: The
Pause to Avoid Rate Limitsnode is set to pause between each entry. You can adjust this time or remove it entirely if you have a small number of workflows and are not concerned about hitting API rate limits.
n8n Workflow Inventory Dashboard with Google Sheets
This n8n workflow helps you create and maintain an inventory dashboard of your n8n workflows in Google Sheets. It's designed to fetch information about your workflows and then organize that data into a spreadsheet for easy tracking and analysis.
What it does
This workflow automates the following steps:
- Triggers Manually or on Schedule: The workflow can be initiated manually with a single click or configured to run automatically at scheduled intervals (e.g., daily, weekly).
- Fetches n8n Workflows: It connects to your n8n instance using the n8n API to retrieve a list of all existing workflows.
- Processes Workflow Data: A Code node processes the raw workflow data, likely extracting key details such as workflow ID, name, status, last execution, etc.
- Loops Through Workflows: The workflow then iterates through each retrieved workflow item, allowing for individual processing.
- Waits (Optional): A "Wait" node is included, which can be configured to introduce a delay between processing each workflow item. This is useful for rate limiting or preventing API overload.
- Updates Google Sheet: For each workflow, it writes or updates a row in a specified Google Sheet, effectively building or maintaining your workflow inventory dashboard.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: An active n8n instance where this workflow will run.
- n8n API Key: Credentials for your n8n instance to allow the workflow to query its own API. This typically involves an API key and a webhook URL or similar authentication.
- Google Account: A Google account with access to Google Sheets.
- Google Sheets Credential: An n8n credential configured for Google Sheets to allow the workflow to write data to your spreadsheet.
- Google Sheet: A pre-existing Google Sheet where the workflow inventory data will be stored. You might need to set up appropriate headers in the first row.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure Credentials:
- n8n API: Configure the "n8n" node (node ID 826) with your n8n API credentials. You'll need to provide your n8n base URL and an API key.
- Google Sheets: Configure the "Google Sheets" node (node ID 18) with your Google Sheets credentials. This typically involves OAuth2 authentication.
- Configure Google Sheet Details:
- In the "Google Sheets" node, specify the Spreadsheet ID and the Sheet Name where you want to store your workflow inventory.
- Adjust Loop and Wait (Optional):
- The "Loop Over Items" (Split in Batches) node (node ID 39) can be configured to process items in batches if needed.
- The "Wait" node (node ID 514) can be adjusted to introduce a specific delay (e.g., 1 second) between processing each workflow if you encounter rate limits or prefer a slower update.
- Activate and Execute:
- Manual Trigger: Click "Execute Workflow" on the "When clicking ‘Execute workflow’" node (node ID 838) to run it once.
- Schedule Trigger: Configure the "Schedule Trigger" node (node ID 839) to run the workflow automatically at your desired interval (e.g., every day at 09:00 AM).
- Ensure the workflow is "Active" to allow scheduled executions.
This workflow provides a robust foundation for monitoring and managing your n8n workflows through a centralized Google Sheets dashboard.
Related Templates
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.
🎓 How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.