CONTENT CREATION
Verify a Refreshed Page Recovered Traffic 30 Days After Publish
Thirty days after a refresh card is marked published in Notion, it re-queries BigQuery to measure whether organic clicks recovered.
How it runs
The automated pipeline, trigger to output.
- TriggerNotion card marked publishedNotion
- LogicWait 30 days post-publish
- ActionQuery post-refresh organic clicksBigQuery
- LogicClassify recovered, partial, or no-change
- ActionUpdate card with outcome in NotionNotion
- OutputPost verdict and re-queue to SlackSlack
What it does
It closes the loop on every refresh. When a card is marked published in Notion, the workflow schedules a check 30 days out. On that date it pulls the page's post-refresh organic clicks from BigQuery, compares them to both the pre-refresh trough and the original baseline, and labels the refresh a recovery, partial, or no-change. The verdict lands on the Notion card and in Slack.
When to use it
Use it to prove content refresh ROI and catch refreshes that didn't move the needle, so you can re-queue them instead of assuming the job is done.
How it works
- 1A Notion status change to "published" triggers the workflow and records the publish date.
- 2The workflow waits 30 days using a scheduled delay.
- 3BigQuery returns the page's clicks for the 28 days following publish.
- 4A logic step classifies the outcome as recovered, partial, or no-change against baseline.
- 5The workflow updates the Notion card with the result and posts the verdict to Slack, re-queuing no-change pages.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.