Claude Code n8n AI-Powered Newsletter Curator

This workflow automates the entire newsletter creation process using Claude Code to build an n8n pipeline that reads from multiple RSS feeds, summarizes articles with Claude or OpenAI, remembers subscriber preferences via Mem0 memory, and sends curated newsletters through Mailchimp. Claude Code in MCP mode constructs a multi-stage n8n workflow with RSS feed nodes, AI processing nodes, Mem0 memory lookup nodes, and Mailchimp campaign nodes. The pipeline runs on a weekly schedule: it fetches the latest articles from 5-10 RSS sources, passes each through an AI summarizer that produces 2-3 sentence summaries, looks up each subscriber's preference profile in Mem0, personalizes the article selection based on past click behavior, compiles the final newsletter, and sends it via Mailchimp. The agentic reasoning step is the article ranking — Claude evaluates each article against Mem0-stored subscriber preferences and decides which articles appear first, which get summarized, and which get omitted. Build time is 15 minutes with Claude Code versus 90+ minutes manually wiring AI and personalization nodes.

BUSINESS PROBLEM

Content marketers spend 6-10 hours per week curating, summarizing, and sending newsletters. For a team managing 3 newsletters across different segments, that is 18-30 hours of repetitive work. According to Litmus's 2025 Email Analytics Report, personalized newsletters see 4.3x higher click-through rates than batch-and-blast sends, but most teams lack the engineering resources to build AI-driven personalization. The manual workflow has three bottlenecks: reading 50+ articles to select the best 5-8, writing unique summaries for each, and segmenting content by subscriber interest. Claude Code and n8n connected via MCP solve all three in a single automated pipeline. RSS feeds feed into an AI summarizer that produces consistent-length summaries. Mem0 stores each subscriber's click history and topic preferences so the newsletter adapts per recipient. Mailchimp handles the delivery. The result is a personalized newsletter sent weekly with zero human curation time.

WHO BENEFITS

FOR content marketing managers at B2B SaaS companies sending 2-4 newsletters per week to segmented audiences SITUATION: You spend 6-10 hours per week reading, summarizing, and manually segmenting newsletter content. PAYOFF: RSS feeds auto-populate. Claude summarizes every article. Mem0 remembers subscriber preferences. Send personalized newsletters in 15 minutes.

FOR newsletter operators with 5,000+ subscribers needing personalization SITUATION: Batch newsletters get 1-2% CTR. Personalized newsletters get 4-5% but require engineering resources. PAYOFF: Mem0 preference memory drives per-subscriber article ranking without custom ML infrastructure.

FOR indie creators running paid newsletters SITUATION: You produce a weekly newsletter but curation takes your entire Friday. PAYOFF: Claude builds the pipeline in 15 minutes. You review the AI draft and hit send.

HOW IT WORKS

1. RSS Feed Setup (Claude Code MCP — 1 min) Input: List of 5-10 RSS feed URLs covering the newsletter topic areas Action: Claude adds multiple RSS Feed Read nodes, each configured with a different source URL and update interval Output: Multi-source article stream with titles, URLs, publish dates, and body content

2. Article Deduplication (Claude Code MCP — 30 sec) Input: Article stream from all RSS sources Action: Claude adds a Code node that deduplicates by URL and title similarity, keeps most recent version Output: Deduplicated article list ranked by publish date

3. AI Summarization (Claude Code MCP — 1 min) Input: Each article's full text content Action: Claude adds an OpenAI node or HTTP node calling Claude API with a summarization prompt requesting 2-3 sentence summaries Output: Summary object per article with title, URL, summary text, and source attribution

4. Mem0 Preference Lookup (Claude Code MCP — 1 min) Input: Subscriber list from Mailchimp Action: Claude adds Mem0 API node that queries stored preferences for each subscriber segment: past clicks, topic affinity scores, skipped topics Output: Per-subscriber preference profile with weighted topic scores

5. Article Ranking (Claude Code MCP — 2 min) Input: Deduplicated summaries + per-subscriber preference profiles Action: Claude adds an AI node that ranks articles by relevance score per subscriber segment, prioritizing topics with high affinity Output: Ranked article list per segment with relevance scores

6. Newsletter Compilation (Claude Code MCP — 1 min) Input: Ranked articles with summaries Action: Claude adds a Code node that builds the newsletter HTML body with top 5-8 articles, intro paragraph, and CTA Output: Compiled newsletter HTML template per segment

7. Mailchimp Campaign Creation (Claude Code MCP — 1 min) Input: Newsletter HTML template, subscriber segments, subject line Action: Claude adds Mailchimp node that creates a new campaign, sets recipients by segment, sets subject line, and schedules send Output: Mailchimp campaign created and scheduled

8. Schedule Setup (Claude Code MCP — 30 sec) Input: Weekly cadence (e.g., Tuesday 8 AM) Action: Claude adds n8n Schedule trigger node with cron expression Output: Automated weekly newsletter execution

TOOL INTEGRATION

n8n v1.80+ Role: Workflow execution and service orchestration Install: npx n8n or n8n.cloud Config step: Enable MCP in Settings, generate access token, restart instance fully Gotcha: RSS Feed Read nodes can timeout on large feeds. Set timeout to 30 seconds per feed.

Claude Code v2.1.154+ Role: AI workflow builder — generates the complete newsletter pipeline via MCP Install: npm install -g @anthropic-ai/claude-code Config step: claude mcp add n8n-mcp with N8N_API_URL and N8N_API_KEY Gotcha: Claude Code can generate nodes faster than n8n can process them. If workflow creation fails, add a 500ms delay between node additions.

OpenAI API / Claude API Role: Article summarization and ranking Config step: API key in n8n credentials Gotcha: Token costs scale with article volume. 50 articles summarized weekly at 2K tokens each costs approximately $1-2 per run.

Mem0 Role: Subscriber preference memory — stores click history and topic affinity per subscriber Config step: Mem0 API key in n8n HTTP Request node Gotcha: Mem0 needs an initial training period. First 2-3 newsletters will have generic ranking until click data accumulates.

Mailchimp Role: Newsletter delivery and subscriber management Config step: Mailchimp API key in n8n credentials Gotcha: Mailchimp rate limits campaign creation to 10 per hour. Schedule sends with spacing.

ROI METRICS

1. Workflow build time: 90 minutes manual to 15 minutes with Claude Code MCP
2. Newsletter production time: 6-10 hours per week to 15 minutes review
3. Click-through rate uplift: 1-2% batch send to 4-5% personalized (Litmus, 2025)
4. Content volume processed: 10-15 articles manually to 50+ articles automatically
5. First-7-day win: First personalized newsletter sent in under 20 minutes of setup

CAVEATS

1. (moderate risk) Mem0 warmup period: Preference memory requires 2-3 newsletter cycles before learning subscriber behavior. Initial sends use generic ranking.
2. (minor risk) AI summary quality variance: Technical articles may produce less accurate summaries than general news.
3. (minor risk) RSS feed unreliability: Some feeds go offline without notice. Add error handling for failed feeds.
4. (significant risk) Token cost at scale: 50 articles per week at 2K tokens each costs $5-15 per run. Monitor costs monthly.