PERSONAL PRODUCTIVITY
AI agent triages orphaned Notion pages: relink or retire
An agent reviews each orphaned, stale Notion page, decides whether it should be linked into a relevant living page or retired.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionGather orphaned stale pages from NotionNotion
- ActionAgent classifies each page relink vs retireOpenAI
- LogicSplit relink and retire paths
- ActionAdd suggested inbound link or archive page in NotionNotion
- OutputPost triage report with reasoning to SlackSlack
What it does
Instead of treating every unreferenced page as dead weight, an agent reads each orphaned, stale page and judges its value. For pages still worth keeping, it finds the most relevant active page and proposes adding an inbound link. For genuinely obsolete pages, it archives them and records a one-line rationale. A Slack report summarizes both buckets.
When to use it
When orphaned pages aren't all junk and a blunt archive sweep would lose useful content that merely lost its links. Use this when you want intelligent triage that rescues valuable orphans by re-integrating them into the knowledge base.
How it works
- 1A weekly schedule kicks off the run.
- 2The workflow gathers orphaned pages past the staleness window from Notion.
- 3For each, the agent reads the content and classifies it as relink or retire, and for relink candidates names a target page.
- 4A logic step splits the two paths.
- 5Relink candidates get a suggested inbound link added in Notion; retire candidates are archived with the rationale.
- 6A Slack report lists relinked and retired pages with the agent's reasoning.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect OpenAIModels, embeddings, files.
- 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 Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
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.
