HumationHuman + Automation
Back to Catalog

🔥📈🤖 AI agent for n8n creators leaderboard - find popular workflows

Joseph LePageJoseph LePage
7237 views
2/3/2026
Google DriveAutomationEmailGmailAttachment
Official Page

n8n Creators Leaderboard Workflow

Why Use This Workflow?

The n8n Creators Leaderboard Workflow is a powerful tool for analyzing and presenting detailed statistics about workflow creators and their contributions within the n8n community. It provides users with actionable insights into popular workflows, community trends, and top contributors, all while automating the process of data retrieval and report generation.

Benefits

  • Discover Popular Workflows: Identify workflows with the most unique visitors and inserters (weekly and monthly).
  • Understand Community Trends: Gain insights into what workflows are resonating with the community.
  • Recognize Top Contributors: Highlight impactful creators to foster collaboration and inspiration.
  • Save Time with Automation: Automates data fetching, processing, and reporting for efficiency.

Use Cases

  • For Workflow Creators: Track performance metrics of your workflows to optimize them for better engagement.
  • For Community Managers: Identify trends and recognize top contributors to improve community resources.
  • For New Users: Explore popular workflows as inspiration for building your own automations.

How It Works

This workflow aggregates data from GitHub repositories containing statistics about workflow creators and their templates. It processes this data, filters it based on user input, and generates a detailed Markdown report using an AI agent.

Key Features

  1. Data Aggregation: Fetches creator and workflow statistics from GitHub JSON files.
  2. Custom Filtering: Focuses on specific creators based on a username provided via chat.
  3. AI-Powered Reports: Generates comprehensive Markdown reports with summaries, tables, and insights.
  4. Output Flexibility: Saves reports locally with timestamps for easy access.

Data Retrieval & Processing

  • Creators Data: Retrieved via an HTTP Request node from a JSON file containing aggregated statistics about creators.
  • Workflows Data: Pulled from another JSON file with workflow metrics like visitor counts and inserter statistics.
  • Data Merging: Combines creator and workflow data by matching usernames to provide enriched statistics.

Report Generation

The AI agent generates a Markdown report that includes:

  • A summary of the creator’s contributions.
  • A table of workflows with key metrics (e.g., unique visitors, inserters).
  • Insights into trends or community feedback.

The report is saved locally as a file with a timestamp for tracking purposes.

Quick Start Guide

Prerequisites

  1. Ensure your n8n instance is running.
  2. Verify that the GitHub base URL and file variables are correctly set in the Global Variables node.
  3. Confirm that your OpenAI credentials are configured for the AI Agent node.

How to Start

  1. Activate the Workflow: Make sure the workflow is active in your n8n environment.
  2. Trigger via Chat: Use the Chat Trigger node to initiate the workflow by sending a message like:
    show me stats for username [desired_username]
    Replace [desired_username] with the username you want to analyze.
  3. Processing & Report Generation: The workflow fetches data, processes it, and generates a Markdown report.
  4. View Output: The final report is saved locally as a file (with a timestamp), which you can review to explore leaderboard insights.

AI Agent for n8n Creators Leaderboard - Find Popular Workflows

This n8n workflow leverages an AI agent to identify and present popular n8n workflows based on a given query. It acts as an intelligent assistant, allowing users to discover relevant and highly-rated workflows from the n8n community or blog.

What it does

This workflow automates the process of finding popular n8n workflows by:

  1. Receiving a Chat Message: It starts by listening for incoming chat messages, which are expected to contain a query about n8n workflows.
  2. Initializing AI Agent: An AI agent is initialized with a simple memory to maintain context during the conversation.
  3. Providing Tools to the AI Agent: The AI agent is equipped with a "Call n8n Workflow Tool" that allows it to execute other n8n workflows. This is crucial for the agent to perform actions like searching for workflows.
  4. Processing Query with AI Agent: The AI agent receives the user's query and, using its tools and understanding, plans how to fulfill the request. This likely involves calling another workflow to perform the actual search.
  5. Responding to the User: After the AI agent processes the query and potentially retrieves information, it formulates a response and sends it back to the user via the chat.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: An active n8n instance to import and run the workflow.
  • AI Agent Credentials:
    • OpenAI API Key or Ollama Chat Model: Depending on your chosen Large Language Model (LLM), you will need either an OpenAI API key configured as an n8n credential, or a running Ollama instance accessible by n8n.
  • Chat Integration: A configured chat service (e.g., Slack, Telegram, Mattermost) that can send messages to the "Chat Trigger" node and receive responses.
  • "Call n8n Workflow Tool" Configuration: The "Call n8n Workflow Tool" node will need to be configured to point to the specific workflow(s) that the AI agent should execute to perform tasks like searching for popular workflows. This implies there's a separate workflow designed for searching/retrieving workflow data.

Setup/Usage

  1. Import the Workflow: Download the JSON definition and import it into your n8n instance.
  2. Configure Chat Trigger: Set up the "When chat message received" node to listen to your preferred chat service and channel.
  3. Configure AI Agent Credentials:
    • If using OpenAI: Ensure your OpenAI API key is configured as a credential in n8n and selected in the "OpenAI Chat Model" node.
    • If using Ollama: Ensure your Ollama instance is running and accessible, and configure the "Ollama Chat Model" node accordingly.
  4. Configure "Call n8n Workflow Tool":
    • Edit the "Call n8n Workflow Tool" node.
    • Specify the Workflow ID of the n8n workflow that the AI agent should call to perform the actual search for popular workflows. This dependent workflow needs to exist and be accessible.
    • Define the Input Schema and Output Schema for the tool, describing what data the AI agent can pass to and expect from the called workflow.
  5. Activate the Workflow: Once configured, activate the workflow.
  6. Interact via Chat: Send a chat message with your query (e.g., "Find popular workflows for data transformation") to the configured chat service. The AI agent will process your request and respond.

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