# n8n: Weekly Competitor Digest — Blogs, Releases, and Pricing Changes

> Track every competitor's blog, changelog, and pricing page in one n8n workflow that emails a summarized weekly digest — no manual monitoring.

**Platform:** n8n  
**Category:** marketing  
**Difficulty:** Intermediate  
**Tags:** n8n, monitoring, competitive-intel, openai  
**Updated:** 2026-06-02  
**Source:** https://promptfoo.tech/workflows/n8n-competitor-monitoring-digest

## Overview
Product marketing dies when nobody watches the competition. This n8n workflow monitors every competitor's blog RSS, GitHub releases, and pricing page, then emails a Monday-morning digest highlighting only what changed since last week.

## How it works
1. A schedule trigger runs weekly on Monday at 07:00.
2. Parallel branches fetch each competitor's RSS, GitHub releases, and pricing page HTML.
3. A hash comparison flags pricing-page changes (byte-diff too noisy alone; semantic diff via LLM finds real changes).
4. New blog posts and releases are summarized with GPT-4o-mini in one sentence each.
5. Everything lands as a single markdown email to the product marketing distro.

## Benefits
- One 10-minute email replaces weekly manual competitor sweeps.
- Pricing changes get caught the week they happen, not next quarter.
- History is searchable in your email — a permanent competitive-intel log.

## Use cases
- Product marketing teams in mid-market SaaS.
- Founders tracking 5-10 direct competitors.
- Agencies producing quarterly competitive intel reports.

## Step-by-step
### Step 1: Build the competitor list once
A JSON file in the workflow: name, blog RSS, GitHub org, pricing URL, focus. Anything else is noise.

### Step 2: Fetch pricing pages with cache-busting headers
Some sites cache aggressively. A cache-control: no-cache header + varying user-agent avoids stale HTML.

### Step 3: Hash-then-LLM for pricing diffs
Compare HTML hash to last week's. If different, send both versions to Claude with 'summarize what changed'. Skips wasted LLM calls.

### Step 4: One-sentence rule for summaries
The digest is skimmable or unread. One sentence per item, max.

### Step 5: Email as markdown, not HTML
Product marketers forward these to Slack. Markdown pastes cleanly; HTML doesn't.

## Example
```
Digest entry: 'Competitor X launched usage-based pricing tier at $0.02/1K events, replacing their flat $99/mo starter. Full changelog: link.'
```

## FAQs
**Why not use a paid competitive intel tool?**

For 5-10 competitors, this workflow costs $2/month in API calls. Paid tools start at $500/month.

**What about paywalled competitors?**

Skip them. Scraping paywalled sites is legally messy and rarely worth it.

**How do I catch social/announcement noise?**

Add an X list monitored via RSS.app. Filter to accounts, not keywords.

---
Licensed under CC-BY-4.0. Attribution: PromptFoo.tech