HumationHuman + Automation
Back to Catalog

Track GitHub node definitions and export to Google Sheets

StefanStefan
100 views
2/3/2026
Google DriveIMAPAutomationEmailAttachment
Official Page

Track n8n Node Definitions from GitHub and Export to Google Sheets

Overview

This workflow automatically retrieves and processes metadata from the official n8n GitHub repository, filters all available .node.json files, parses their structure, and appends structured information into a Google Sheet. Perfect for developers, community managers, and technical writers who need to maintain up-to-date information about n8n's evolving node ecosystem.

Setup Instructions

Prerequisites

Before setting up this workflow, ensure you have:

  • A GitHub account with API access
  • A Google account with Google Sheets access
  • An active n8n instance (cloud or self-hosted)

Step 1: GitHub API Configuration

  1. Navigate to GitHub Settings → Developer Settings → Personal Access Tokens
  2. Generate a new token with public_repo permissions
  3. Copy the generated token and store it securely
  4. In n8n, create a new "GitHub API" credential
  5. Paste your token in the credential configuration and save

Step 2: Google Sheets Setup

  1. Create a new Google Sheets document
  2. Set up the following column headers in the first row:
    • node (Column A) - Node identifier/name
    • nodeVersion (Column B) - Version of the node
    • codexVersion (Column C) - Codex version number
    • categories (Column D) - Node categories
    • credentialDocumentation (Column E) - Credential documentation URL
    • primaryDocumentation (Column F) - Primary documentation URL
  3. Note down the Google Sheets document ID from the URL
  4. Configure Google Sheets OAuth2 credentials in n8n

Step 3: Workflow Configuration

  1. Import the workflow into your n8n instance
  2. Update the following placeholder values:
    • Replace YOUR_GOOGLE_SHEETS_DOCUMENT_ID with your actual document ID
    • Replace YOUR_WEBHOOK_ID if using webhook functionality
  3. Configure the GitHub API credentials in the HTTP Request nodes
  4. Set up Google Sheets credentials in the Google Sheets nodes
  5. Share your Google Sheets document with the email address associated with your Google OAuth2 credentials
  6. Grant "Editor" permissions to allow the workflow to write data

Google Sheets Template Details

The workflow creates a structured dataset with these columns:

  • node: Node identifier (e.g., n8n-nodes-base.slack)
  • nodeVersion: Version of the node (e.g., 1.0.0)
  • codexVersion: Codex version number (e.g., 1.0.0)
  • categories: Node categories (e.g., Communication, Productivity)
  • credentialDocumentation: URL to credential documentation
  • primaryDocumentation: URL to primary node documentation

Customization Options

Modifying Data Extraction

You can customize the "Format Data" node to extract additional fields:

  • Add new assignments in the Set node
  • Modify the column mapping in the Google Sheets node
  • Update your spreadsheet headers accordingly

Changing Update Frequency

To run this workflow on a schedule:

  1. Replace the Manual Trigger with a Cron node
  2. Set your desired schedule (e.g., daily, weekly)
  3. Configure appropriate timing to avoid API rate limits

Adding Filters

Customize the "Filter Node Files" code node to:

  • Filter specific node types
  • Include/exclude certain categories
  • Process only recently updated nodes

Features

  • Fetches all node definitions from the n8n-io/n8n repository
  • Filters for .node.json files only
  • Downloads and parses metadata automatically
  • Extracts key fields like node names, versions, categories, and documentation URLs
  • Appends structured data to Google Sheets with batch processing
  • Includes error handling and retry mechanisms
  • Clears existing data before appending new information for fresh results

Use Cases

This workflow is ideal for:

  • Track changes in official n8n node definitions over time
  • Audit node categories and documentation links for completeness
  • Build custom dashboards from node metadata
  • Community management and documentation maintenance
  • Integration planning and compatibility analysis

n8n Workflow: GitHub Node Definition Extractor and Google Sheets Exporter

This n8n workflow is designed to fetch and process GitHub node definitions, then export the extracted data to a Google Sheet. It's a manual trigger workflow, allowing you to run it on demand to update your records.

What it does

This workflow performs the following steps:

  1. Manual Trigger: Initiates the workflow when you manually click "Execute workflow" in n8n.
  2. HTTP Request: Makes an HTTP request to a specified URL (likely a GitHub API endpoint or a raw file URL) to retrieve data, presumably containing node definitions.
  3. Edit Fields (Set): Processes the data received from the HTTP request. This node is typically used to transform, rename, or filter fields, preparing the data for the next steps.
  4. Loop Over Items (Split in Batches): If the data contains multiple items (e.g., an array of node definitions), this node will split them into batches, allowing subsequent operations to process each item individually or in smaller groups.
  5. Code: Executes custom JavaScript code. This node is likely used for advanced data manipulation, parsing, or formatting of the node definitions before they are exported.
  6. Wait: Introduces a pause in the workflow. This can be useful for respecting API rate limits or allowing time for external systems to process previous steps.
  7. Google Sheets: Appends the processed node definition data as new rows to a specified Google Sheet.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • 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.
  • GitHub Data Source: The URL for the GitHub node definitions you wish to track. This will be configured within the "HTTP Request" node.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" to create a new workflow.
    • Click the "Import from JSON" button (usually a {} icon) and paste the workflow JSON.
  2. Configure Credentials:
    • Locate the "Google Sheets" node.
    • Click on the "Credential" field and select an existing Google Sheets credential or create a new one. Follow the n8n documentation for setting up Google Sheets credentials if needed.
  3. Configure HTTP Request:
    • Locate the "HTTP Request" node.
    • Update the "URL" field to point to the specific GitHub API endpoint or raw file URL containing the node definitions you want to track.
    • Configure any necessary authentication (e.g., API keys, headers) if the GitHub source requires it.
  4. Configure Google Sheets:
    • Locate the "Google Sheets" node.
    • Specify the "Spreadsheet ID" and "Sheet Name" where you want the data to be exported.
    • Ensure the "Operation" is set to "Append Row" or similar, and map the incoming data fields to the correct columns in your Google Sheet.
  5. Review and Customize:
    • Examine the "Edit Fields (Set)" and "Code" nodes. You may need to adjust their configurations based on the exact structure of the data returned by your GitHub source and how you want it to appear in Google Sheets.
    • Adjust the "Wait" node's duration if necessary.
  6. Execute the Workflow:
    • Click the "Execute Workflow" button (play icon) in the n8n editor to run the workflow manually.
    • Verify that the data is correctly extracted and appended to your Google Sheet.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942