HumationHuman + Automation
Back to Catalog

Monitor hotel competitor rates and answer WhatsApp Q&A using OpenAI GPT-4.1

Lee LinLee Lin
56 views
2/3/2026
Google SheetsSlackNotificationsAutomationEmail
Official Page

How It Works

Top Branch Workflow A

1. The Market Intelligence:

  • Patrols the Market: Runs hourly to scrape competitor rates for future days.
  • Gathers Intel: If prices spike, it instantly checks event announcements to see if a major event is driving demand.
  • Crunches Numbers: Calculates the exact price gap and filters out noise.

2. The Revenue Manager:

  • Sets Strategy: The AI Agent reviews the price gaps, competitor moves, and event signals.
  • Reports: Writes a strategic Executive Summary and sends it to your WhatsApp.

Bottom Branch Workflow B

3. The Consultant:

  • Recall: When you ask a question via WhatsApp, the bot retrieves the saved analysis, historical rates, and event schedule.
  • Answer: It acts as an on-demand analyst, conducting further analysis to give an informed answer to questions

Setup Steps

1. Config: Add your hotel + competitor hotels (IDs/names) in the Config node.

2. Monitor Window: Set how far ahead you want to monitor (e.g., daysAhead = 30) in the Config node.

3. Sensitivity: Set how sensitive alerts should be (e.g., alert only if competitor moves > 10%) in the Significant Competitor Change node.

4. Connect Credentials:

  • Amadeus (to fetch hotel prices)
  • WhatsApp (to send alerts)
  • Postgres/SQL (to store price snapshots, history, summary)
  • OpenAI (for the AI Agents)

5. Event Source: Update the Fetch VCC nodes to scrape your local convention center or event site.

6. Run a test:

Trigger Workflow A manually and confirm you receive a WhatsApp alert.

Reply to that WhatsApp message to test Workflow B (Q&A).

Use Cases & Benefits

For Revenue Managers: Automate the "rate shop" routine and catch competitor moves without opening a spreadsheet.

For Sales & Marketing Teams: Go beyond raw data. Pairing "what changed" with "why changed" instantly.

For Hotel Leadership: Perfect for GMs and division leaders who need instant, decision-ready alerts via WhatsApp.

⚡ Zero-Touch Efficiency: Eliminates hours of manual searching by automating rate checks 3x daily. 🧠 Contextual Intelligence: Tracks price AND explains why it moved by cross-referencing local events. 🤖 Actionable Strategy: AI doesn't just report numbers; it recommends specific pricing tactics. 📉 Long-Term Vision: Builds a permanent database of rate history, enabling the AI to answer complex trend questions over time.

Screenshot 20260118 at 12.56.34 PM.pngScreenshot 20260118 at 12.57.01 PM.png

📬 Want to Customize This?

leelin.business@gmail.com

n8n Workflow: Hotel Competitor Rate Monitoring and WhatsApp AI QA

This n8n workflow provides a comprehensive solution for monitoring hotel competitor rates and leveraging an AI agent to answer WhatsApp queries based on the gathered information. It combines scheduled web scraping, data processing, and conversational AI to keep you informed and responsive.

What it does

This workflow automates the following key steps:

  1. Scheduled Rate Scraping: Periodically fetches hotel competitor rates from a specified URL using an HTTP Request node.
  2. HTML Data Extraction: Parses the HTML response to extract relevant rate information using the HTML node.
  3. Data Structuring: Transforms the extracted HTML data into a structured format (likely a data table) for further processing.
  4. AI Agent for WhatsApp QA:
    • Listens for WhatsApp Messages: Triggers when a new message is received via WhatsApp.
    • Processes Incoming Messages: Uses an AI Agent (powered by an OpenAI Chat Model and Simple Memory) to understand the user's query.
    • Accesses Rate Data: The AI Agent is likely configured to use the scraped hotel rate data as a knowledge source to answer questions about competitor rates.
    • Generates Structured Output: The AI's response is processed by a Structured Output Parser.
    • Sends WhatsApp Reply: Responds to the user's WhatsApp message with the AI-generated answer.
  5. Conditional Logic: Includes an 'If' node, suggesting conditional processing or routing based on certain criteria (e.g., if new rates are found, or if a WhatsApp message requires AI intervention).
  6. Data Merging: A 'Merge' node indicates that different data streams or processing paths are combined at some point in the workflow.
  7. Field Editing: A 'Set' node is used to manipulate or add fields to the data, ensuring it's in the correct format for subsequent nodes.
  8. Code Execution: A 'Code' node allows for custom JavaScript logic, providing flexibility for specific data transformations or API interactions not covered by standard nodes.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to host and execute the workflow.
  • WhatsApp Business Cloud Account: Configured credentials for the WhatsApp Business Cloud to send and receive messages.
  • OpenAI API Key: Credentials for OpenAI to power the AI Chat Model and Agent.
  • Target Website for Scraping: The URL of the hotel competitor website you wish to monitor for rates.
  • Basic understanding of HTML/CSS selectors: To configure the HTML node for accurate data extraction.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your WhatsApp Business Cloud credentials in n8n.
    • Set up your OpenAI credentials in n8n.
  3. Configure Schedule Trigger: Adjust the "Schedule Trigger" node to your desired interval for monitoring competitor rates (e.g., daily, hourly).
  4. Configure HTTP Request: Update the "HTTP Request" node with the URL of the hotel competitor website you want to scrape.
  5. Configure HTML Node: Customize the "HTML" node with the appropriate CSS selectors to extract the specific rate information you need from the target website.
  6. Configure AI Agent and Models:
    • Review the "AI Agent" node's configuration, ensuring it's set up to use the "OpenAI Chat Model" and "Simple Memory".
    • Adjust the prompt or instructions within the "AI Agent" to guide its responses regarding hotel rates.
  7. Configure WhatsApp Trigger: Ensure the "WhatsApp Trigger" node is correctly configured to listen for incoming messages.
  8. Activate the Workflow: Once all configurations are complete, activate the workflow.

The workflow will then automatically scrape competitor rates at your defined schedule and use an AI agent to answer WhatsApp queries about these rates.

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