CONTENT CREATION

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.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerchat
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack slash command with page IDSlack
  • ActionLook up screenshots for the pageAirtableAirtable
  • ActionFetch current release versionGitHubGitHub
  • LogicScore by age and version gap; sort worst-first
  • OutputReply with ranked regeneration checklistSlack

What it does

A docs writer asks for a freshness check on one page via Slack. The workflow pulls every screenshot on that page, scores each by how old it is and how many releases behind it was captured, and replies in-thread with a ranked list of which images to regenerate first.

When to use it

Use it when someone is about to revise a specific docs page and wants a quick verdict on which screenshots are too stale to keep, without waiting for a scheduled audit or scanning the whole library.

How it works

  1. 1A Slack slash command with a page identifier triggers the run.
  2. 2The workflow looks up the screenshots embedded on that page from the screenshot metadata store.
  3. 3It fetches the current release version from GitHub for comparison.
  4. 4A logic step scores each image by capture age and version gap, then sorts worst-first.
  5. 5It replies in the same Slack thread with a ranked checklist, marking any image more than two releases behind as urgent.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.