Track brand visibility on Perplexity and ChatGPT with BrowserAct and OpenRouter

Workflow preview

100%

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

1. Workflow Overview

Track brand visibility on Perplexity and ChatGPT with BrowserAct & OpenRouter Introduction This workflow acts as a "Generative Engine Optimization" (GEO) tracker. It automatically monitors how your...

Best for

Market Research automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.lmchatopenrouter, n8n-nodes-browseract.browseract, n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.merge, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.slack

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Madame AI Team | Kai.

Original n8n.io source

1.1 Workflow description

Title: Track brand visibility on Perplexity and ChatGPT with BrowserAct and OpenRouter
Workflow name: Track brand visibility on Perplexity and ChatGPT with BrowserAct and OpenRouter

Track brand visibility on Perplexity and ChatGPT with BrowserAct & OpenRouter

Introduction

This workflow acts as a "Generative Engine Optimization" (GEO) tracker. It automatically monitors how your brand is being recommended on AI-powered search engines by simulating real user queries on Perplexity and ChatGPT, analyzing the responses for visibility and sentiment, and reporting the findings to Slack.

Target Audience

Brand managers, SEO specialists, and marketing teams who need to monitor their "share of voice" in AI search results.

How it works

Scheduling: A Weekly Trigger initiates the workflow to ensure regular monitoring of your brand's presence.
Context Setup: A Set node defines the target Brand name and a brief Description of the value proposition.
Query Generation: An AI Agent (using OpenRouter/GPT-4o) reads the brand details and generates two distinct search queries:

Research Query: Targeted at Perplexity (e.g., "Top rated tools for X in 2025").
Conversational Query: Targeted at ChatGPT (e.g., "I need advice on X, what do you recommend?").

Parallel Execution: The workflow splits into two parallel paths to maximize efficiency.
Data Extraction: Two separate BrowserAct nodes execute the generated queries on Perplexity and ChatGPT respectively. They scrape the full text of the AI's response.
Synchronization: A Merge node waits for both scraping tasks to complete before proceeding.
Analysis: A second AI Agent acts as a "GEO Analyst." It compares the scraped answers against your Brand Name to determine if the brand was "Visible" (recommended), "Invisible" (ignored), or "Hallucinated." It also grades the sentiment.
Reporting: A Slack node posts a formatted report detailing the visibility status on both platforms.

How to set up

Configure Credentials: Connect your BrowserAct, OpenRouter, and Slack accounts in n8n.
Prepare BrowserAct: Ensure the AI Search Visibility Tracker (Perplexity & ChatGPT) template is saved in your BrowserAct account.
Define Brand: Open the Add Brand & Description node. Update the Brand field with your company name and the Description field with your core offering.
Select Slack Channel: Open the Send team update node and select the channel where reports should be posted.

Requirements

BrowserAct Account: Required for scraping the AI platforms. Template: AI Search Visibility Tracker (Perplexity & ChatGPT).
OpenRouter Account: Required for generating queries and analyzing the sentiment of the results.
Slack Account: Required for receiving the final visibility report.

How to customize the workflow

Add More Engines: Clone the BrowserAct node to add checks for Google Gemini or Claude, then connect them to the Merge node.
Track Competitors: Modify the Add Brand & Description node to input a competitor's name instead of your own to see how AI recommends them.
Store History: Add a Google Sheets node before the Slack step to log the "Sentiment Score" and "Visibility Status" over time for trend analysis.

Need Help?

Workflow Guidance and Showcase Video

AI SEO Reporting: Automated Brand Mentions Tracking for Teams

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 - OpenRouter Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 2 - Run a Perplexity Search

Type / Role: n8n-nodes-browseract.browserAct - browserAct
Config choices: Version 1

Block 3 - Run ChatGPT Search

Type / Role: n8n-nodes-browseract.browserAct - browserAct
Config choices: Version 1

Block 4 - OpenRouter Chat Model1

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 5 - Weekly Trigger

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

Block 6 - Add Brand & Description

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 7 - Wait for both paths

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 8 - Analyze both results & generate report

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3

Block 9 - Structured Output

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 10 - Structured Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 11 - Send team update

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.4

Block 12 - Generate search queries

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3

Block 13 - Documentation

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

Block 14 - Step 1 Explanation

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

Block 15 - Step 2 Explanation

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

Block 16 - Step 3 Explanation

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

Block 17 - Sticky Note

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

3. Summary Table

Workflow	Track brand visibility on Perplexity and ChatGPT with BrowserAct and OpenRouter
Complexity	advanced
Nodes	17
Categories	Market Research, AI Summarization
Author	Madame AI Team \| Kai
Published	13 Feb 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/13378/13378.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 AI Summarization workflows

Frequently asked questions

What does Track brand visibility on Perplexity and ChatGPT with BrowserAct and OpenRouter 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, AI Summarization use case.

Madame AI Team | Kai

50 workflows

Nodes

@n8n/n8n-nodes-langchain.lmchatopenrouter n8n-nodes-browseract.browseract n8n-nodes-base.scheduletrigger n8n-nodes-base.set n8n-nodes-base.merge @n8n/n8n-nodes-langchain.agent @n8n/n8n-nodes-langchain.outputparserstructured n8n-nodes-base.slack

Complexity

advanced

Published 13 Feb 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/13378/13378.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.

Track brand visibility on Perplexity and ChatGPT with BrowserAct and OpenRouter

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Track brand visibility on Perplexity and ChatGPT with BrowserAct & OpenRouter

Introduction

Target Audience

How it works

How to set up

Requirements

How to customize the workflow

Need Help?

Workflow Guidance and Showcase Video

AI SEO Reporting: Automated Brand Mentions Tracking for Teams

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - OpenRouter Chat Model

Block 2 - Run a Perplexity Search

Block 3 - Run ChatGPT Search

Block 4 - OpenRouter Chat Model1

Block 5 - Weekly Trigger

Block 6 - Add Brand & Description

Block 7 - Wait for both paths

Block 8 - Analyze both results & generate report

Block 9 - Structured Output

Block 10 - Structured Output Parser

Block 11 - Send team update

Block 12 - Generate search queries

Block 13 - Documentation

Block 14 - Step 1 Explanation

Block 15 - Step 2 Explanation

Block 16 - Step 3 Explanation

Block 17 - Sticky Note

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