HumationHuman + Automation
Back to Catalog

Intelligent web query and semantic re-ranking flow using Brave and Google Gemini

Mind-FrontMind-Front
5221 views
2/3/2026
Google SheetsSynchronizationAutomationEventsGoogle Calendar
Official Page

Workflow Description

This workflow is a powerful, fully automated web query and semantic reranking system that allows users to perform precise, detailed searches, intelligently rank search results and provide high-quality, structured output. Built with AI-powered components, the workflow leverages semantic query generation, result re-ranking, and real-time reporting to deliver actionable insights.

It is particularly well-suited for real-time data retrieval, market research, and any domain requiring automated yet customizable search result processing.

How It Works

  1. Webhook Integration for Input:

    • The workflow begins with a Webhook Node that captures the user's search query as input, enabling seamless integration with other systems.

  2. Step 1: Semantic Query Generation (Powered by "Semantic Search - Query Maker"):

    • Using AI (Google Gemini), the initial query is refined and transformed into a context-aware, expert-level search query.
    • The process ensures that the search engine retrieves the most relevant and precise results.

  3. Step 2: Web Search Execution:

    • A free Brave Search API processes the refined query to fetch search results, ensuring speed and cost efficiency.

  4. Step 3: Semantic Re-Ranking of Results (Powered by "Semantic Search - Result Re-Ranker"):

    • The workflow reranks the search results based on relevance to the original question, prioritizing the most relevant URLs dynamically.
    • Results are passed through AI-powered intelligent reranking to ensure the final output reflects optimal relevance and quality.

  5. Step 4: Structured Output Generation:

    • Results are converted into a well-structured, organized JSON format, ranking the top 10 search results with their titles, links, and descriptions.
    • Missing ranks (if fewer than 10 results) are handled gracefully with placeholders, ensuring consistency.

  6. Step 5: Real-Time Reporting:

    • The reranked search results are sent back to the user or integrated system via the Webhook Node in a JSON-formatted response.
    • Reports are highly structured and ready for downstream processing or consumption.

Key Features

  1. AI-Powered Query Refinement:

    • Transforms basic queries into detailed, expert-level search terms for optimal results.

  2. Dual-Stage Semantic Search:

    • Combines query generation and result reranking for precise, high-relevance outputs.

  3. Top 10 Result Reranking:

    • Dynamically ranks and organizes the top 10 results based on semantic relevance to the query.

  4. Customizable Integration:

    • Fully modifiable for alternative APIs or integrations, such as other search engines or custom ranking logic.

  5. JSON-Formatted Structured Results:

    • Outputs reranked results in a standardized format, ideal for integration into systems requiring machine-readable data.

  6. Webhook-Based Flexibility:

    • Works seamlessly with Webhook inputs for easy deployment in diverse workflows.

  7. Cost-Effective API Usage:

    • Pre-integrated with the free Brave Search API, minimizing operational costs while delivering accurate search results.

Instructions for API Setup

  1. Brave Search API:
  2. AI Integration (Google Gemini):
    • Visit Google AI Studio and generate an API key for semantic query generation and reranking.
  3. Webhook Configuration:
    • Set up the input Webhook to capture search queries and the output Webhook to deliver reranked results.

Why Choose This Workflow?

  • Precision and Relevance: Combines AI-based query generation with advanced reranking for accurate results.
  • Fully Customizable: Easily adapt the workflow to alternative APIs, search engines, or ranking logic.
  • Real-Time Insights: Provides structured, real-time output ready for immediate use.
  • Scalable and Modular: Ideal for businesses, researchers, and data analysts needing a robust, repeatable solution.

Tags

AI Workflow, Semantic Search, Query Refinement, Search Result Reranking, Real-Time Search, Web Search Automation, Google Search, Brave Search, News Search, API Integration, Market Research, Competitive Intelligence, Business Intelligence,Google Gemini, Anthropic Claude, OpenAI, GPT, LLM

Intelligent Web Query and Semantic Re-ranking Flow using Brave and Google Gemini

This n8n workflow provides a powerful solution for performing intelligent web queries and semantically re-ranking the results. It leverages the Brave Search API for initial web searches and Google Gemini (or other LLMs) for advanced semantic analysis and re-ranking, delivering more relevant and contextually rich results.

What it does

This workflow automates the following steps:

  1. Receives a Webhook Trigger: The workflow starts by listening for an incoming webhook, which is expected to contain the search query.
  2. Performs a Brave Search: It makes an HTTP request to the Brave Search API, using the provided query to fetch initial web search results.
  3. Processes Search Results: The raw search results are then processed.
  4. Generates Semantic Re-ranking with LLM: The core of the intelligence lies here. It utilizes a Language Model (specifically Google Gemini Chat Model in the current configuration, but can be switched to OpenAI or Anthropic) within a Basic LLM Chain to semantically analyze and re-rank the search results based on the original query.
  5. Formats Output: The re-ranked results are then formatted into a structured output using a Structured Output Parser, potentially with an Auto-fixing Output Parser for robustness.
  6. Responds to Webhook: Finally, the workflow sends the semantically re-ranked search results back as a response to the original webhook trigger.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Brave Search API Key: An API key for Brave Search to perform web queries.
  • Google Gemini API Key (or OpenAI/Anthropic API Key): An API key for Google Gemini (or OpenAI/Anthropic if you switch the LLM node) to power the semantic re-ranking.
  • Credentials in n8n: You will need to configure credentials in n8n for your Brave Search API and your chosen LLM (Google Gemini, OpenAI, or Anthropic).

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up a credential for the HTTP Request node (Node ID: 19) to authenticate with the Brave Search API.
    • Set up a credential for the Google Gemini Chat Model node (Node ID: 1262) using your Google Gemini API key. If you decide to use OpenAI or Anthropic, configure their respective credentials.
  3. Activate the Webhook: Once imported, activate the Webhook node (Node ID: 47) to get its URL.
  4. Send a Query: Send an HTTP POST request to the webhook URL with your search query in the request body. The workflow expects the query to be passed as part of the webhook data.

Example Webhook Request (JSON body):

{
  "query": "best practices for n8n workflow documentation"
}

The workflow will then process your query, fetch results from Brave Search, semantically re-rank them using Google Gemini, and return the enhanced results in the webhook response.

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