HumationHuman + Automation
Back to Catalog

Analyze browsing history and generate automation suggestions with OpenRouter AI and Google Sheets

Msaid Mohamed el hadiMsaid Mohamed el hadi
523 views
2/3/2026
Google SheetsTrelloAutomationProductivityData Sync
Official Page

🧠 Browsing History Automation Analyzer – Automation Toolkit (Google Sheets + AI)

This n8n workflow analyzes your browsing history to identify opportunities for automation. It reads history from a Google Sheet, groups visits by domain, filters out irrelevant entries, and uses AI to recommend what can be automated — including how and why.

📌 What It Does

  • 📄 Reads your browsing history from Google Sheets
  • 🌐 Groups history by domain
  • 🚫 Filters out common non-actionable domains (e.g., YouTube, Google)
  • 🤖 Uses AI to analyze whether your activity on each site is automatable
  • 💡 Provides suggestions including what to automate, how to do it, and which tools to use
  • 📝 Saves results into a new tab in the same Google Sheet
  • 🔍 Searches for n8n workflow templates related to the suggested automation

📊 Demo Sheet

Input + output are handled via the following Google Sheet:

📎 Spreadsheet:
View on Google Sheets

  • Sheet: history → Input browsing history
  • Sheet: automations → Output AI automation suggestions

🧠 AI Analysis Logic

The AI agent receives each domain's browsing history and responds with:

  • domain: The website domain
  • automatable: true/false
  • what_to_automate: Specific actions that can be automated
  • reason: Why it's suitable (or not) for automation
  • tool: Suggested automation tool (e.g., n8n, Apify)
  • automation_rating: High, Medium, Low, or Not Automatable
  • n8n_template: Relevant automation template (if found)

🔧 Technologies Used

| Tool | Purpose | |--------------------------|-------------------------------------| | n8n | Workflow automation | | LangChain AI Agent | AI-based analysis | | Google Sheets Node | Input/output data handling | | OpenRouter (LLM) | Language model for intelligent reasoning | | JavaScript Code Node | Grouping and formatting logic | | Filter Node | Remove unwanted domains | | HTTP Request Node | Search n8n.io templates |

💻 Chrome History Export

You can use this Chrome extension to export your browsing history in a format compatible with the workflow:

🔗 Export Chrome History Extension

📧 Want Personalized Automation Advice?

If you'd like personalized automation recommendations based on your browsing history—just like what this workflow provides—feel free to contact me directly:

> 📩 msaidwolfltd@gmail.com

I'll help you discover what tasks you can automate to save time and boost productivity.

🚀 Example Use Cases

  • Automate daily logins to dashboards
  • Auto-fill forms on repetitive websites
  • Schedule data exports from web portals
  • Trigger reminders based on recurring visits
  • Discover opportunities for scraping and integration

📜 License

This workflow is provided as-is for educational and personal use. For commercial or customized use, contact the author.

n8n Workflow: Analyze Browsing History and Generate Automation Suggestions with OpenRouter AI and Google Sheets

This n8n workflow automates the process of analyzing browsing history data from a Google Sheet, identifying patterns, and generating actionable automation suggestions using an AI agent powered by OpenRouter.

What it does

This workflow performs the following key steps:

  1. Triggers Manually: The workflow is initiated manually, allowing for on-demand analysis.
  2. Reads Browsing History: It connects to a specified Google Sheet to retrieve browsing history data.
  3. Loops Through Data: It processes the retrieved browsing history data in batches, allowing for efficient handling of large datasets.
  4. Filters Data (Placeholder): Includes a filter node, which can be configured to filter browsing history items based on specific criteria (e.g., exclude certain websites, focus on specific timeframes).
  5. Prepares Data for AI: A Code node is used to transform and format the browsing history data into a suitable prompt for the AI agent.
  6. Analyzes with AI Agent: An AI Agent node (powered by LangChain) uses a conversational memory and an OpenRouter Chat Model to analyze the browsing history. It identifies repetitive tasks, common patterns, and potential areas for automation.
  7. Generates Automation Suggestions: The AI Agent generates practical automation suggestions based on its analysis of the browsing history.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Access to a Google Sheet containing your browsing history data.
  • OpenRouter API Key: An API key for OpenRouter to access their AI models.
  • n8n Credentials: Configured credentials for Google Sheets and OpenRouter within your n8n instance.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" to create a new workflow.
    • Go to the "Workflows" menu, click "Import from JSON", and paste the copied JSON.
  2. Configure Google Sheets Node:
    • Click on the "Google Sheets" node.
    • Select or create a Google Sheets credential.
    • Specify the "Spreadsheet ID" and "Sheet Name" where your browsing history data is located.
    • Ensure the "Operation" is set to "Read" and "Return All" or configure as needed.
  3. Configure OpenRouter Chat Model:
    • Click on the "OpenRouter Chat Model" node (nested within the "AI Agent").
    • Select or create an OpenRouter credential using your API key.
    • Choose your preferred OpenRouter model.
  4. Configure Code Node (if necessary):
    • Review the "Code" node. It's currently set up to prepare the browsing history for the AI. Adjust the JavaScript logic if your browsing history data structure differs or if you need specific pre-processing.
  5. Configure Filter Node (optional):
    • If you wish to filter your browsing history before AI analysis, configure the "Filter" node with your desired conditions.
  6. Activate and Execute:
    • Save the workflow.
    • Click the "Execute Workflow" button on the "Manual Trigger" node to run the workflow.
    • Observe the output of the "AI Agent" node for the generated automation suggestions.

This workflow provides a powerful starting point for gaining insights into your digital habits and leveraging AI to streamline your daily tasks.

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