n8n 3-in-1 AI Automation Suite

This 81-node n8n workflow portfolio uses Claude API (Anthropic's Claude 3.5 Sonnet) and Gemini API (Google's Gemini 1.5 Pro) to run three distinct AI-powered automation systems from a single n8n instance: a content factory that researches, drafts, and publishes SEO blog posts to WordPress; a customer intelligence engine that scrapes support tickets and review sites to surface sentiment trends and feature requests; and a multi-agent campaign orchestrator that coordinates email sequences, social posts, and retargeting across Google Sheets plans. The agentic reasoning step in each subsystem is unique — the content factory's Claude agent evaluates topic clusters for keyword overlap and content gap before drafting, while the intelligence engine's Gemini agent scores customer sentiment on a 5-axis rubric. The measurable outcome: a 3-person marketing team produces what previously required 8 people, saving 12-20 hours weekly across content, research, and campaign management.

BUSINESS PROBLEM

A B2B SaaS marketing team of 3 people manages 12 blog posts per month, monitors 4 customer feedback channels, and runs 2 campaigns simultaneously. They estimate 60% of their collective time goes to manual research, copy-pasting between tools, and formatting content for different channels. A 2024 Gartner survey found that marketing teams spend 31% of their total work hours on content production and distribution logistics — not strategy or creative work (Source: Gartner Marketing Technology Survey, 2024). For a 3-person team at $75,000 average salary each, that is $69,750 per year burned on logistics alone. The n8n 3-in-1 suite eliminates these logistics by connecting the content pipeline, customer data pipeline, and campaign pipeline into one visual workflow layer — no custom code, no Zapier dependency, no context-switching between tools.

WHO BENEFITS

B2B SaaS marketing teams of 2-5 people managing content, support insights, and campaigns simultaneously: you currently juggle 8-12 SaaS tools with no central automation layer. This suite consolidates content, intelligence, and campaigns into one n8n dashboard.

Content agencies handling 5-10 client accounts: you need separate but identical workflows per client. n8n's template system lets you clone the 81-node suite per client with different API keys and Google Sheet IDs — no rebuilding.

Solo founders running all marketing: you are writer, analyst, and campaign manager in one person. Automating all three functions lets you produce what a 3-person team would, at one person's cost.

HOW IT WORKS

1. Content Factory — Topic Research. Claude API analyzes your existing blog posts, competitor URLs, and keyword data from Google Sheets. It identifies content gaps (topics competitors cover that you do not). Output: prioritized topic list with search volume estimates.

2. Content Factory — Drafting. Claude API generates a 1,500-2,000 word blog post per topic, including headlines, body sections, and meta description. It follows your style guide stored in Google Sheets. Output: formatted draft in Google Sheets.

3. Content Factory — Publishing. n8n's WordPress node pushes the draft as a new post with featured image (generated via DALL-E or stock API), categories, and tags. Output: published post.

4. Customer Intelligence — Data Collection. Gemini API scrapes new support tickets and review site mentions via API or RSS. It categorizes each item as bug, feature request, or sentiment mention. This is the agentic reasoning step: Gemini scores sentiment on a 5-axis rubric.

5. Customer Intelligence — Trend Report. Gemini summarizes weekly trends into a report written to Google Sheets. Output: structured trend dashboard.

6. Campaign Orchestrator — Plan Ingestion. n8n reads campaign plans from a Google Sheet (channels, dates, content assets). Output: structured campaign JSON.

7. Campaign Orchestrator — Multi-Channel Dispatch. Claude API adapts each content asset for email (Mailchimp node), social (Twitter/LinkedIn nodes), and blog. Output: scheduled posts across all channels.

TOOL INTEGRATION

n8n (self-hosted or cloud, latest). Role: visual workflow orchestrator connecting all tools. API key: configured via n8n instance settings. Scope: HTTP requests, database queries, file system access. Rate limit: depends on your n8n instance — cloud has 2,500 executions/month limit on the free plan. Gotcha: n8n's Claude API node requires the HTTP Request node configured with Anthropic's API format — the dedicated Claude node in older n8n versions may not support Claude 3.5 Sonnet. Use the HTTP Request node with Bearer token auth instead.

Claude API (Anthropic, Claude 3.5 Sonnet). Role: content generation and campaign adaptation. API key: from console.anthropic.com. Scope: text generation only. Rate limit: Tier 1 allows 5 requests/minute. Gotcha: Claude's output occasionally includes markdown formatting even when you request plain text — add a post-processing step in n8n to strip markdown before publishing.

Gemini API (Google, Gemini 1.5 Pro). Role: sentiment analysis and trend detection. API key: from aistudio.google.com. Scope: text analysis. Rate limit: 60 requests/minute on the free tier. Gotcha: Gemini 1.5 Pro's 1M token context can slow response times for large inputs — split support ticket batches into chunks of 50-100 tickets per request to stay under 5-second response targets.

Google Sheets (via n8n Google Sheets node). Role: shared data store for topic lists, drafts, sentiment data, and campaign plans. Authentication: OAuth 2.0 via Google Cloud Console. Scope: read/write access to specified sheets. Rate limit: 60 requests/user/minute. Gotcha: the n8n Google Sheets node sometimes fails silently on rate-limit exceeded — add an error-handling webhook to retry after 60 seconds.

WordPress (via n8n WordPress node). Role: content publishing destination. Authentication: Application Password or OAuth. Scope: create and update posts. Rate limit: depends on your hosting provider. Gotcha: the WordPress node may not support custom post types by default — use the HTTP Request node with WordPress REST API for CPT support.

ROI METRICS

1. Content production time: 8-12 hours per published post (research + writing + formatting + publishing) → 1-2 hours for review and editing only
2. Customer insight turnaround: 4-6 hours per weekly trend report, assembled manually from support tools → 10 minutes automated via Gemini analysis
3. Campaign deployment speed: 3-5 days from content creation to multi-channel live → 4-6 hours from Google Sheets plan to deployed
4. First-week measurable: number of blog posts published with no manual editing — target is 2 posts in week one
5. Tools consolidated: 8-12 separate SaaS tools → 1 n8n instance + 4 API integrations

CAVEATS

1. API cost scaling: three APIs (Claude, Gemini, and possibly a third for images) running 50+ operations daily can reach $200-400/month. Monitor each API's cost dashboard weekly.
2. Workflow brittleness: 81 nodes means 81 potential failure points. A broken Google Sheets node can halt content, intelligence, and campaigns simultaneously. Build error-handling branches for every node.
3. Content quality variability: Claude-generated drafts may need editing for brand voice consistency. Review the first 10 posts before setting the workflow to fully automated publishing.
4. Does not handle: video production, podcast creation, or paid ad management (Google Ads, Meta Ads).