Find top keywords for Youtube and Google and store them in NocoDB

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

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

1. Workflow Overview

Template Description WDF Top Keywords : This workflow is designed to streamline keyword research by automating the process of generating, filtering, and analyzing Google and YouTube keyword data. E...

Best for

Market Research automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.stickynote, n8n-nodes-base.nocodb, n8n-nodes-base.httprequest, n8n-nodes-base.splitout, n8n-nodes-base.filter

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Find top keywords for Youtube and Google and store them in NocoDB
Workflow name: Find top keywords for Youtube and Google and store them in NocoDB

Template Description
WDF Top Keywords: This workflow is designed to streamline keyword research by automating the process of generating, filtering, and analyzing Google and YouTube keyword data. Ensure compliance with local regulations and API terms of service when using this workflow.

📌 Purpose
The WDF Top Keywords workflow automates collecting, processing, and managing keyword data for both Google and YouTube platforms. Leveraging multiple data sources and APIs ensures an efficient and scalable approach to identifying high-impact keywords for SEO, content creation, and marketing campaigns.

Key Features

Automates the generation of keyword suggestions using autocomplete APIs.
Integrates with NocoDB to store and manage keyword data.
Filters keywords based on monthly search volume and cost-per-click (CPC).
Supports bulk import of keyword data into structured databases.
Outputs both Google and YouTube keyword insights, enabling informed decision-making.

🎯 Target Audience
This workflow is ideal for:

Digital marketers aiming to optimize ad campaigns with data-driven insights.
SEO specialists looking to identify high-potential keywords efficiently.
Content creators seeking trending and relevant topics for their platforms.
Agencies managing keyword research for multiple clients.

⚙️ How It Works

Trigger: The workflow runs on-demand or at scheduled intervals.
Keyword Generation:
- Retrieves base keywords from NocoDB.
- Generates autocomplete suggestions for Google and YouTube.
Data Processing:
- Filters and formats keyword data based on specific criteria (e.g., search volume, CPC).
- Consolidates results for efficient storage and analysis.
Storage and Output:
- Saves data into structured NocoDB tables for tracking and reuse.
- Bulk imports monthly search volume statistics for detailed analysis.

🛠️ Key APIs and Tools Used

NocoDB: Stores and organizes base and processed keyword data.
DataForSEO API: Provides search volume and keyword performance metrics.
Google Autocomplete API: Suggests relevant Google search terms.
YouTube Autocomplete API: Suggests trending YouTube keywords.
Social Flood Docker Instance: Serves as the local integration hub.

Setup Instructions

Required Tools:
Create the following NocoDB tables:
- Base Keyword Search
- Second Order Google Keywords
- Second Order YouTube Keywords
- Search Volume

This template empowers users to handle complex keyword research tasks effortlessly, saving time and providing actionable insights. Share this template to enhance your workflow efficiency!

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 - When clicking ‘Test workflow’

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

Block 2 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 3 - Gen Time

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

Block 4 - Sticky Note

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

Block 5 - Sticky Note1

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

Block 6 - Sticky Note2

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

Block 7 - NocoDB

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

Block 8 - Second Order Google Autocomplete Keywords

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

Block 9 - Google Search Volume

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

Block 10 - Sticky Note3

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

Block 11 - Split Out Google Search

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

Block 12 - YouTube Search Volume

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

Block 13 - Second Order YouTube Autocomplete Keywords

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

Block 14 - Split Out YT Search

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

Block 15 - Google Filter

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.2

Block 16 - YT Filter

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.2

Block 17 - Add Second Tier YT Keyword Data

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

Block 18 - Add Second Tier G Keyword Data

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

Block 19 - Format G Data

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

Block 20 - Format YT Data

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

Block 21 - Bulk Import G Monthly Search Volume

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

Block 22 - Bulk Import YT Monthly Search Volume

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

Block 23 - Sticky Note4

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

Block 24 - Is Google Keyword Available

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Showing the first 24 of 35 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Find top keywords for Youtube and Google and store them in NocoDB
Complexity	advanced
Nodes	35
Categories	Market Research
Author	Shannon Atkinson
Published	12 Feb 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/2884/2884.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Market Research workflows

Frequently asked questions

What does Find top keywords for Youtube and Google and store them in NocoDB do?

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 Market Research use case.

Shannon Atkinson

1 workflow

Nodes

n8n-nodes-base.manualtrigger n8n-nodes-base.scheduletrigger n8n-nodes-base.code n8n-nodes-base.stickynote n8n-nodes-base.nocodb n8n-nodes-base.httprequest n8n-nodes-base.splitout n8n-nodes-base.filter

Complexity

advanced

Published 12 Feb 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/2884/2884.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

## Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. ## How it works 1. The workflow listens for new messages in a designated Microsoft Teams channel or chat. 2. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. 3. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. 4. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. 5. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). 6. A final Claude agent translates the raw query results into a concise, plain-English summary. 7. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. 8. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. ## Setup 1. CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. 2. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. 3. Configure your Google BigQuery credentials to allow reading metadata and executing queries. 4. Configure your Anthropic credentials for the three Claude LangChain nodes. 5. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. ## Requirements - A Google Cloud project with BigQuery enabled and existing structured datasets. - An Anthropic API key with access to the Claude 3.5 Sonnet model. - Microsoft Teams administrator access to authorize the n8n integration. ## Customization - Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. - UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. ## Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

View

Evaluate LinkedIn profiles with Apify and Groq Llama chat model

## Quick overview This workflow collects a LinkedIn profile URL via an n8n form, scrapes the public profile data using the Apify LinkedIn Profile Scraper actor, analyzes the results with a Groq-hosted Llama model, and displays an HTML-formatted evaluation back to the user. ## How it works 1. Receives a LinkedIn Profile URL when a user submits the n8n form. 2. Prepares the LinkedIn URL along with the Apify API token and Groq API key used for downstream requests. 3. Sends the profile URL to the Apify `harvestapi/linkedin-profile-scraper` actor and retrieves the scraped dataset items. 4. Passes the scraped profile JSON to a Groq chat model via an LLM chain to generate an HTML evaluation with a score and recommendations. 5. Displays the generated HTML evaluation to the user as the form completion message. ## Setup 1. Add a valid Apify API token and ensure the Apify actor endpoint (`harvestapi/linkedin-profile-scraper`) is accessible for your account. 2. Add Groq API credentials in n8n and confirm the selected model (meta-llama/llama-4-scout-17b-16e-instruct) is available to your Groq account. 3. Replace the placeholder API key values in the workflow (or move them to n8n credentials/environment variables) and verify the form field label matches `LinkedIn Profile URL`.

View

Validate startup ideas with Google Gemini, Groq, and Gmail

## Quick overview This workflow collects a startup idea via an n8n form, uses Google Gemini to generate a SWOT-style analysis, assigns a viability score, uses Groq to turn the results into a structured validation report, and emails the final report through Gmail. ## How it works 1. Receives a startup idea, industry, and target audience from an n8n Form trigger. 2. Sends the submission to Google Gemini to generate a professional analysis covering the problem, business model, and SWOT factors. 3. Generates a startup viability score (currently a random value from 80–100) and packages it with the Gemini analysis. 4. Sends the score and analysis to Groq (Llama 3.3 70B) to compile a full validation report with an executive summary, market potential, recommendations, and final verdict. 5. Emails the generated validation report to the configured recipient using Gmail. ## Setup 1. Add credentials for Google Gemini (PaLM) API, Groq API, and a Gmail OAuth2 connection. 2. Replace the placeholder recipient address in the Gmail step ("[email protected]") with your target email address before activating the workflow. 3. Publish the n8n form, then share the form URL with the users who should submit their startup ideas for validation.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Find top keywords for Youtube and Google and store them in NocoDB

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Key Features

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - When clicking ‘Test workflow’

Block 2 - Schedule Trigger

Block 3 - Gen Time

Block 4 - Sticky Note

Block 5 - Sticky Note1

Block 6 - Sticky Note2

Block 7 - NocoDB

Block 8 - Second Order Google Autocomplete Keywords

Block 9 - Google Search Volume

Block 10 - Sticky Note3

Block 11 - Split Out Google Search

Block 12 - YouTube Search Volume

Block 13 - Second Order YouTube Autocomplete Keywords

Block 14 - Split Out YT Search

Block 15 - Google Filter

Block 16 - YT Filter

Block 17 - Add Second Tier YT Keyword Data

Block 18 - Add Second Tier G Keyword Data

Block 19 - Format G Data

Block 20 - Format YT Data

Block 21 - Bulk Import G Monthly Search Volume

Block 22 - Bulk Import YT Monthly Search Volume

Block 23 - Sticky Note4

Block 24 - Is Google Keyword Available

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions