n8n Competitor Monitoring: Track Websites, Pricing, and Content Automatically
Keeping tabs on your competitors is not optional — it is a survival skill. But manually checking competitor websites, pricing pages, and social accounts every day is a terrible use of your time. By the time you notice a change, your competitors may have already captured your customers.
I am Javier, a startup consultant in Chile, and I have built competitive intelligence systems for startups that need to move fast. With n8n, I set up automated monitoring that watches competitors around the clock and alerts the team only when something important changes. No noise, no manual checking, just actionable intelligence delivered to your inbox or Slack.
In this guide, I will show you how to build a complete competitor monitoring system with n8n.
Why Use n8n for Competitor Monitoring?
Dedicated competitive intelligence tools like Crayon, Klue, or Kompyte cost hundreds of dollars per month and often include features you do not need. n8n lets you build exactly the monitoring you want, connected to the tools you already use.
What n8n handles well:
– Website change detection — monitor specific pages and get alerted when content changes
– Pricing surveillance — track competitor pricing pages and detect changes automatically
– Content monitoring — watch for new blog posts, case studies, and feature announcements
– Social media tracking — monitor competitor social accounts for new posts and engagement patterns
– Job posting analysis — track what roles competitors are hiring for (signals about their strategy)
– Review monitoring — watch for new reviews on G2, Capterra, and other platforms
Setting Up n8n for Competitor Monitoring
The foundation of competitor monitoring is scheduled web scraping and change detection.
If you do not have n8n running yet, start with n8n cloud. Monitoring workflows run on schedules and need reliable uptime to avoid missing changes.
Core Components
Data collection: HTTP Request nodes to fetch web pages, RSS Trigger for blog monitoring
Change detection: Function nodes to compare current content with stored versions
Storage: A database or Google Sheet to store snapshots and historical data
Alerts: Slack, email, or your preferred notification channel
Workflow 1: Website Change Detection
The most fundamental monitoring workflow. It watches specific pages on competitor websites and alerts you when anything changes.
How It Works
Trigger: Schedule Trigger running every 6 hours (or more frequently for critical pages)
Step 1: Fetch the page. Use an HTTP Request node to download the competitor’s page. For each competitor, monitor their most strategic pages:
– Pricing page
– Features page
– Homepage (for messaging changes)
– Product changelog or “What’s New” page
Step 2: Extract relevant content. The raw HTML contains too much noise (navigation, ads, scripts). Use a Function node to:
– Strip HTML tags and keep only the text content
– Remove whitespace and normalize formatting
– Focus on the main content area by targeting specific CSS selectors or HTML elements
– Generate a hash of the cleaned content for quick comparison
Step 3: Compare with stored version. Query your storage (Google Sheet, database, or n8n’s built-in static data) for the last known version of this page. Compare the content hashes.
Step 4: If changed, analyze the difference. Use a Function node to identify what specifically changed:
– New text that was not there before
– Removed text
– Changed numbers (especially on pricing pages)
For deeper analysis, send both the old and new versions to OpenAI with a prompt like: “Compare these two versions of a competitor’s pricing page. List every change you find, focusing on pricing, plan names, feature inclusions, and any new or removed offerings.”
Step 5: Alert and store. If a meaningful change is detected:
1. Send a Slack notification to your #competitive-intel channel with the page URL, a summary of changes, and a timestamp
2. Update the stored version with the new content
3. Log the change in your competitive intelligence database with the date and details
Handling Dynamic Content
Some competitor pages load content dynamically with JavaScript, which means a simple HTTP Request will not see the full page. For these cases, use a headless browser approach: call a service like ScrapingBee or Browserless via HTTP Request, which renders the JavaScript and returns the fully loaded HTML.
Workflow 2: Pricing Page Monitor
Pricing changes deserve their own specialized workflow because they are the most actionable competitive intelligence.
Trigger: Schedule Trigger running every 4 hours
1. Fetch each competitor’s pricing page — one HTTP Request per competitor
2. Extract pricing data with a structured approach:
– Plan names and their prices
– Feature lists for each plan
– Any promotional pricing or discounts
– Enterprise pricing indicators (“Contact us” versus a listed price)
3. Compare with stored pricing data — this is more structured than general page monitoring. Store pricing as JSON objects so you can compare individual fields
4. Detect specific changes:
– Price increase or decrease on any plan
– New plan added or plan removed
– Features moved between plans (common competitive move)
– New feature added to any plan
– Free tier changes
5. Generate an alert with context:
– What changed
– Previous value versus new value
– Percentage change for price modifications
– Your team’s recommended response
I also maintain a historical pricing spreadsheet that updates automatically. This lets you spot pricing trends over months — are competitors gradually raising prices? Are they consolidating plans?
Workflow 3: Content and Blog Monitoring
Track when competitors publish new content to understand their marketing strategy and positioning.
Trigger: RSS Trigger monitoring each competitor’s blog RSS feed (check every 2 hours)
Most company blogs have RSS feeds. Common URL patterns: /blog/feed, /blog/rss, /feed, /rss.xml
1. When a new post appears in the feed, extract the title, URL, publication date, and summary
2. Fetch the full article using an HTTP Request node to get more context
3. Classify the content using OpenAI: “Classify this blog post into one of these categories: product_update, case_study, thought_leadership, comparison_post, tutorial, company_news. Also identify the primary topic and any products or features mentioned.”
4. Check for competitive mentions — Does the post mention your company or product? This is high-priority intelligence
5. Send categorized alerts:
– Product updates: alert product team in #product channel
– Comparison posts (especially if they compare against you): alert marketing team immediately
– Case studies: alert sales team with the customer name and industry
– General content: add to a weekly digest
Content Velocity Tracking
A separate scheduled workflow that measures how much content each competitor publishes:
– Posts per week/month
– Topics they focus on
– Content formats (blog, video, podcast, webinar)
– Publishing patterns (which days they publish most)
This data goes into a monthly competitive content report that helps your marketing team adjust their content strategy.
Workflow 4: Job Posting Monitor
What a company is hiring for tells you a lot about their strategy. If a competitor suddenly posts 10 engineering jobs, they are likely building something new.
Trigger: Schedule Trigger running daily
1. Check competitor career pages — Fetch their careers or jobs page via HTTP Request
2. Extract job listings — Parse the page to get job titles, departments, and locations
3. Compare with previous scan — Identify new postings and removed postings
4. Analyze trends:
– Lots of sales hires: expanding to new markets
– AI/ML engineering hires: building AI features
– Enterprise sales hires: moving upmarket
– Customer success hires: scaling their customer base
5. Weekly summary — A digest of all new competitor job postings with strategic implications
Workflow 5: Review and Sentiment Monitoring
Track what customers say about your competitors on review platforms.
Trigger: Schedule Trigger running daily
1. Check review platforms — Use HTTP Request to scrape or API to query G2, Capterra, Trustpilot for new reviews of competitor products
2. Extract review data — Rating, title, pros, cons, and date
3. Analyze sentiment and themes — Use AI to categorize complaints and praise:
– Common complaints (these are opportunities for your product)
– Common praise (these are table-stakes features you must match)
– Trend changes (is sentiment improving or declining?)
4. Flag actionable reviews:
– Negative competitor reviews that mention problems your product solves — potential leads for your sales team
– Positive reviews mentioning features you lack — product gap analysis
5. Monthly report — Competitor review summary with average ratings, review velocity, and top themes
Building Your Competitive Intelligence Dashboard
Bring all the monitoring data together into a single view:
1. Central database — Use Notion, Airtable, or Google Sheets as your competitive intelligence hub
2. Automated updates — Every monitoring workflow writes its findings to the database
3. Weekly digest — A scheduled workflow compiles the week’s competitive intelligence into a formatted report sent to leadership and relevant teams
4. Alert priorities — Critical changes (pricing, direct competitive content) get immediate Slack alerts. Everything else goes into the weekly digest
Tips for Effective Competitor Monitoring
Focus on Actionable Intelligence
Do not monitor everything. Focus on signals that should trigger a response from your team:
– Pricing changes that affect your positioning
– Feature launches that overlap with your roadmap
– Content that directly compares against your product
– Strategic hires that signal new directions
Respect Rate Limits and Terms of Service
Space out your requests to avoid overwhelming competitor servers. A check every 4-6 hours is plenty for most pages. Use reasonable User-Agent headers. Do not scrape content that is behind login walls or paywalls.
Reduce False Positives
Website pages change for many reasons that are not meaningful — updated copyright years, new testimonials rotating in, minor CSS changes. Use content hashing on the meaningful text content only, strip dates and timestamps before comparing, and set minimum change thresholds to avoid alerting on trivial updates.
Keep Historical Data
Store every snapshot, not just the current version. Historical data reveals trends that point-in-time monitoring misses. A competitor that raises prices by 5 percent every quarter is making a strategic move. A competitor that changes their positioning every month is struggling with product-market fit.
Start Monitoring Your Competitive Landscape
You do not need a six-figure competitive intelligence platform to stay informed. A few well-designed n8n workflows can give you continuous visibility into what your competitors are doing, delivered directly to the channels where your team already works.
Start with the pricing page monitor — it provides the most directly actionable intelligence. Then add the blog and content monitor. Build up from there based on what your team finds most valuable.
Get started with n8n and set up your first competitor monitoring workflow today.
Frequently Asked Questions
Is it legal to scrape competitor websites for monitoring?
Monitoring publicly available information on competitor websites is generally acceptable and is a standard business practice. However, you should not scrape content that is behind login walls, violate a website’s terms of service, or overwhelm their servers with excessive requests. Keep your scraping frequency reasonable (every few hours, not every few seconds), respect robots.txt directives, and focus on extracting facts (prices, feature lists) rather than copying copyrighted content. When in doubt, consult with your legal team about specific monitoring activities.
How many competitors should I monitor?
I recommend starting with 3 to 5 direct competitors — the companies your prospects most frequently compare you against. Monitoring too many competitors dilutes your focus and creates information overload. As your system matures and your team gets comfortable with the intelligence flow, you can expand to include indirect competitors or adjacent market players. Quality of analysis matters more than breadth of monitoring.
Can I use n8n to monitor competitor social media activity?
Yes, with some limitations. For platforms with public APIs (like Twitter/X), you can use the API to fetch competitor posts and engagement metrics. For platforms without easy API access (like LinkedIn or Instagram), you can monitor RSS feeds of their content, use third-party services that aggregate social data, or set up HTTP Request nodes to check publicly accessible profile pages. The key constraint is respecting each platform’s rate limits and terms of service.