CONTENT CREATION

Weekly Screenshot Staleness Digest to Slack

Once a week, rolls up the current screenshot-drift inventory across all doc pages into a ranked digest and posts it to a Slack channel so the docs team can plan re-capture work.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead accumulated drift records from PostgresPostgreSQLPostgres
  • LogicGroup by page and rank by weighted severity
  • ActionFormat ranked digest of top offenders
  • OutputPost digest to the docs Slack channelSlack

What it does

Gives the docs team a single weekly view of where screenshot debt is piling up. It tallies which doc pages have the most drifted or aging screenshots, ranks them by severity and reader traffic, and posts a readable digest to Slack so the team can prioritize re-capture work in planning.

When to use it

Use it when you already detect drift but lack a regular, prioritized summary to drive action. Per-image issues are easy to ignore individually; a weekly ranked rollup makes the overall trend and the worst offenders impossible to miss.

How it works

  1. 1A weekly schedule triggers the digest.
  2. 2The flow reads the accumulated drift records from Postgres, where prior audit runs store per-screenshot staleness scores and last-verified dates.
  3. 3A logic step groups records by doc page, scores each page by drift severity weighted by traffic, and ranks them.
  4. 4It formats the top offenders into a compact digest with counts, scores, and direct links.
  5. 5The digest is posted to the docs team's Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.