Auto-Refresh CMS Content Weekly with Claude + n8n + Sanity
Build a hands-free content pipeline that uses Claude to rewrite and update your Sanity articles on a schedule, keeping everything fresh without manual editing.
Tools Used
Purpose
Why this workflow exists
Workflow Steps
Add an autoRefresh boolean and lastUpdated date field to your Sanity article schema. Mark which articles should be auto-refreshed.
Create an n8n workflow with a weekly cron trigger. It queries Sanity's API for all articles where autoRefresh is true and lastUpdated is older than 7 days.
For each article, send the body to Claude API with a prompt: update facts, add current trends, improve clarity, keep the same tone and structure. Return structured JSON.
Use n8n's HTTP node to call Sanity's mutation API, patching each article with the refreshed content and updating the lastUpdated timestamp.
Add a final n8n step that sends a Slack message summarizing which articles were refreshed, with links to review each one before they go live.
Expected Results
What this workflow should unlock
What you get at the end
Build a hands-free content pipeline that uses Claude to rewrite and update your Sanity articles on a schedule, keeping everything fresh without manual editing.
content automation
Operational upside
Instead of rethinking the process each time, you reuse the same sequence across planning, execution, and refinement with Anthropic Claude API, n8n, Sanity.
repeatable execution
Team-facing outcome
Add an autoRefresh boolean and lastUpdated date field to your Sanity article schema. Mark which articles should be auto-refreshed.
less manual coordination
Next-level refinement
Add a final n8n step that sends a Slack message summarizing which articles were refreshed, with links to review each one before they go live.
easy to iterate
Common Questions
Quick answers before you start
What is the main purpose of Auto-Refresh CMS Content Weekly with Claude + n8n + Sanity?
Build a hands-free content pipeline that uses Claude to rewrite and update your Sanity articles on a schedule, keeping everything fresh without manual editing.
How many tools do I actually need to start?
You can usually start with the core set listed here. This idea currently references 3 tools, but you do not need to adopt every tool on day one.
Is this workflow suitable for my experience level?
Yes, as long as you treat the current setup as intermediate. The workflow structure stays the same; the difference is how much customization and orchestration you add.
How long does it take to put this into practice?
Most teams can stand up an initial version quickly because the workflow already breaks into 5 concrete steps. The refinement phase usually takes longer than the first draft.