CONTENT CREATION

Weekly screenshot staleness audit with a Slack report

Once a week, compare each documented screenshot's capture date against the last deploy that touched its route and post a Slack report ranking the most overdue screenshots.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionRead manifest with last-capture timestamps
  • ActionFind last route-touching deploy per screenGitHubGitHub
  • LogicFlag and rank screenshots stale vs their route
  • OutputPost ranked staleness report to SlackSlack

What it does

Produces a prioritized staleness report: for every documented screenshot it checks when the image was last captured versus when its underlying route last shipped, then posts a Slack summary of which screens are most overdue for a refresh.

When to use it

You want visibility and a backlog to work from rather than automatic regeneration — a weekly nudge so the team knows which docs images are lying and by how much.

How it works

  1. 1A weekly schedule triggers the audit.
  2. 2The flow reads the screenshot manifest with each image's last-capture timestamp.
  3. 3For each route it queries the GitHub commit history to find the last deploy that touched it.
  4. 4A logic step flags every screenshot captured before its route's latest change and computes a staleness age.
  5. 5It sorts the flagged set by age.
  6. 6A Slack message posts the ranked list of overdue screenshots with route links.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  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.