CONTENT CREATION
Detect Decaying Pages from Analytics and Draft Refresh Briefs
On a weekly schedule, scans your published pages for organic-traffic decline, re-crawls the decayed URLs, and writes a prioritized refresh brief for each one into Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery 90-day traffic deltas per URLPostgres
- LogicKeep URLs with significant decline, rank by lost sessions
- ActionRe-crawl decayed pages for current contentFirecrawl
- ActionDraft structured refresh briefOpenAI
- OutputCreate brief in Notion refresh queueNotion
What it does
It finds pages whose organic traffic has slid over the trailing 90 days, re-reads what's actually on each page, and produces a concrete refresh brief — what's stale, what to add, and which keywords slipped — so writers start from a plan instead of a hunch.
When to use it
Run it when you have a library of evergreen content and no systematic way to know which posts are quietly losing rankings. Ideal for content teams that publish faster than they audit and want a steady weekly queue of high-leverage updates rather than ad-hoc rewrites.
How it works
- 1A weekly schedule fires the run.
- 2A Postgres query pulls per-URL traffic for the last 90 vs. prior 90 days from your warehoused analytics table.
- 3A logic step keeps only URLs with a meaningful decline (e.g. >25% drop, minimum traffic floor) and ranks them by lost sessions.
- 4Firecrawl re-crawls each surviving URL to capture current title, headings, and body.
- 5OpenAI compares the live content against the decline signal and drafts a structured brief: stale claims, missing subtopics, suggested new sections, and target keywords.
- 6Each brief is written as a new page in a Notion "Content Refresh Queue" database, tagged with priority and lost-traffic estimate.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect FirecrawlCrawl, scrape, structured extract.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.