The blog agent
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Rarely used nodes in this template: n8n-nodes-base.linearTool
Nodes used (10)
- MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - Linear Tool
n8n-nodes-base.linearTool - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Anthropic Chat Model
@n8n/n8n-nodes-langchain.lmChatAnthropic - AI Agent
@n8n/n8n-nodes-langchain.agent - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets Tool
n8n-nodes-base.googleSheetsTool - Http Request Tool
n8n-nodes-base.httpRequestTool - Think Tool
@n8n/n8n-nodes-langchain.toolThink - Chat Trigger
@n8n/n8n-nodes-langchain.chatTrigger
What it does
The Blog Agent Description An intelligent content automation system that manages the complete blog content lifecycle, from strategic planning to publish-ready articles. It combines AI-powered research, SEO-optimized writing, and strategic content management to execute a pillar/cluster content strategy that establishes thought leadership and drives organic search performance. Overview This automation workflow orchestrates a multi-agent system to continuously produce high-quality blog content for Trigify.io. It intelligently manages content strategy, conducts focused research, and generates complete, SEO-optimized blog posts that follow best practices for both traditional search engines and AI-powered search platforms. The system maintains state across multiple content projects, tracks completion status, and ensures consistent brand positioning throughout all content. 🔄 Workflow Process 1. Schedule Trigger Automated content pipeline activation - Runs weekly on Mondays, Tuesdays, and Wednesdays - Triggers the content lifecycle management process - Ensures consistent content production cadence - Can also be manually triggered via chat interface 2. Blog Status Manager Agent Strategic content lifecycle orchestration - Queries Linear API to retrieve all previously written blog posts - Cross-references completed blogs with Google Sheets strategy state - Updates blog statuses from PLANNED to DRAFTCREATED when content exists in Linear - Identifies next priority blog topic from existing pillar/cluster strategy - Selects topics marked as PLANNED for content creation - When all current content is complete, analyzes SEO Report to identify new high-priority pillars - Creates new pillar/cluster strategies based on SEO opportunities - Updates Google Sheets with new content plans and status changes - Passes selected blog topic to Researcher Agent with clear instructions 3. Google Sheets Integration Centralized content strategy management - StrategyState Sheet: Tracks current pillar, cluster statuses, and progress - SEO Report Sheet: Contains comprehensive SEO analysis and keyword opportunities - Maintains real-time state of content pipeline - Stores pillar/cluster relationships and completion tracking - Enables data-driven content prioritization 4. Researcher Agent Fast, focused content research - Receives blog topic from Blog Status Manager Agent - Conducts efficient research using FireCrawl MCP (maximum 2 calls) - Gathers competitor information and market statistics - Creates comprehensive blog briefs with structured outlines - Defines content type (PILLAR or CLUSTER) and word count targets - Specifies metadata requirements (title ≤60 chars, description ≤160 chars) - Identifies image requirements with source URLs - Documents key data points and sources for attribution - Plans internal linking strategy - Defines Trigify positioning angle and CTA - Outputs structured brief for Blog Writer Agent 5. Blog Writer Agent Complete, publish-ready content generation - Receives comprehensive blog brief from Researcher Agent - Conducts additional research using FireCrawl MCP tools - Writes complete blog posts following pillar/cluster structure: - Pillar Posts: 2,000-3,000+ words, resource hub style - Cluster Posts: 800-1,500 words, focused deep-dives - Implements SEO optimization: - Creates metadata within strict character limits - Implements strategic internal linking - Positions Trigify as the primary solution - Uses target keywords naturally throughout content - Ensures brand consistency: - Avoids em dashes (uses parentheses, commas, colons) - Provides real source URLs (never temporary screenshot links) - Includes proper image instructions with public source URLs - Maintains Trigify-first positioning - Generates complete, publish-ready articles (not summaries) - Formats content with proper markdown structure - Creates Linear issue with full blog post content 6. FireCrawl MCP Integration Web scraping and research capabilities - Enables web scraping for