HumationHuman + Automation
Back to Catalog

Brand visibility & sentiment analysis across AI search tools (OpenAI, Perplexity, ChatGPT)

AOE Agent LabAOE Agent Lab
734 views
2/3/2026
parserjsonemailwebhookhttp
Official Page

This n8n template demonstrates how to audit your brand’s visibility across multiple AI systems and automatically log the results to Google Sheets. It sends the same prompt to OpenAI, Perplexity, and (optionally) a ChatGPT web actor, then runs sentiment and brand-hierarchy analysis on the responses.

Use cases are many: benchmark how often (and how positively) your brand appears in AI answers, compare responses across models, and build a repeatable “AI visibility” report for marketing and comms teams.

💡 Good to know

  • You’ll bring your own API keys for OpenAI and Perplexity. Usage costs depend on your providers’ pricing.
  • The optional APIfy actor automates the ChatGPT web UI and may violate terms of service. Use strictly at your own risk.

⁉ How it works

  • A Manual Trigger starts the workflow (you can replace it with any trigger).
  • Input prompts are read from a Google Sheet (or you can use the included “manual input” node).
  • The prompt is sent to three tools: -- OpenAI (via API) to check baseline LLM knowledge. -- Perplexity (API) to retrieve an answer with citations. -- Optionally, an APIfy actor that scrapes a ChatGPT response (web interface).
  • Responses are normalized and mapped (including citations where available).
  • An LLM-powered sentiment pass classifies each response into: -- Basic Polarity: Positive, Neutral, or Negative -- Emotion Category: Joy, Sadness, Anger, Fear, Disgust, or Surprise -- Brand Hierarchy: ordered list such as Nike>Adidas>Puma
  • The consolidated record (Prompt, LLM, Response, Brand mentioned flag, Brand Hierarchy, Basic Polarity, Emotion Category, Source 1–3/4) is appended to your “Output many models” Google Sheet.
  • A simplified branch shows how to take a single response and push it to a separate sheet.

🗺️ How to use

  • Connect your Google Sheets OAuth and create two tabs: -- Input: a single “Prompt” column -- Output: columns for Prompt, LLM, Response, Brand mentioned, Brand Hierarchy, Basic Polarity, Emotion Category, Source 1, Source 2, Source 3, Source 4
  • Add your OpenAI and Perplexity credentials.
  • (Optional) Add an APIfy credential (Query Auth with token) if you want the ChatGPT web actor path.
  • Run the Manual Trigger to process prompts in batches and write results to Sheets.
  • Adjust the included “Limit for testing” node or remove it to process more rows.

⚒️ Requirements

  • OpenAI API access (e.g., GPT-4.1-mini / GPT-5 as configured in the template)
  • Perplexity API access (model: sonar)
  • Google Sheets account with OAuth connected in n8n
  • (Optional) APIfy account/token for the ChatGPT web actor

🎨 Customising this workflow

  • Swap the Manual Trigger for a webhook or schedule to run audits automatically.
  • Extend the sentiment analyzer instructions to include brand-specific rules or compliance checks.
  • Track more sources (e.g., additional models or vertical search tools) by duplicating the request→map→append pattern.
  • Add scoring (e.g., “visibility score” per prompt) and charts by pointing the output sheet into Looker Studio or a BI tool.

Brand Visibility & Sentiment Analysis Across AI Search Tools

This n8n workflow is designed to automate the process of analyzing brand visibility and sentiment across various AI search tools like OpenAI and Perplexity. It fetches brand-related queries from a Google Sheet, processes each query through an AI agent for sentiment analysis, and then records the results.

What it does

  1. Triggers Manually: The workflow is initiated manually, allowing for on-demand analysis.
  2. Reads Brand Queries: It reads a list of brand-related queries from a specified Google Sheet.
  3. Limits Processing: For testing or controlled execution, it can limit the number of queries processed.
  4. Loops Through Queries: It processes each brand query individually in a batch.
  5. Analyzes with AI Agent: For each query, it uses an AI Agent (powered by an OpenAI Chat Model) to perform sentiment analysis. This agent also leverages a Perplexity tool to gather information.
  6. Parses AI Output: The AI Agent's output is parsed into a structured format to extract relevant sentiment data.
  7. Saves Results (Placeholder): The workflow includes a "No Operation" node, indicating a placeholder where the analyzed sentiment data would typically be saved or further processed (e.g., written back to a Google Sheet, sent to a reporting tool, etc.).

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: Access to a Google Sheet containing brand queries.
  • OpenAI API Key: Credentials for the OpenAI Chat Model.
  • Perplexity API Key: Credentials for the Perplexity tool used by the AI Agent.
  • LangChain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed in your n8n instance for AI Agent, Basic LLM Chain, OpenAI Chat Model, and Structured Output Parser nodes.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New Workflow" or the "+" icon.
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Locate the "Google Sheets" node (ID: 18) and configure your Google Sheets credentials. Specify the Spreadsheet ID and Sheet Name where your brand queries are located.
    • Locate the "OpenAI Chat Model" node (ID: 1153) and configure your OpenAI API credentials.
    • Locate the "Perplexity" node (ID: 1304) and configure your Perplexity API credentials.
  3. Review AI Agent Configuration:
    • The "AI Agent" node (ID: 1119) is configured to use the OpenAI Chat Model and the Perplexity tool. Review its prompt and configuration to ensure it aligns with your sentiment analysis requirements.
  4. Customize Output Handling:
    • The "No Operation, do nothing" node (ID: 26) currently acts as a placeholder. You will likely want to replace or connect this to a node that saves the processed data (e.g., another Google Sheets node to write results, a database node, a reporting tool, etc.).
  5. Execute the Workflow:
    • Click the "Execute Workflow" button on the "Manual Trigger" node (ID: 838) to run the workflow.
    • Monitor the execution to ensure data is processed correctly.

This workflow provides a robust foundation for automating brand visibility and sentiment analysis using powerful AI tools.

Related Templates

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88