CONTENT CREATION
Nightly Scan for Doc Screenshots Older Than the Current Release
Runs nightly, compares the app version embedded in each docs screenshot's metadata against the latest shipped release.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionList screenshots and capture versionsAWS S3
- ActionFetch latest release tagGitHub
- LogicFind images behind current release; rank by gap
- ActionFile a Linear issue per stale screenshotLinear
- OutputPost drift summary to SlackSlack
What it does
This workflow audits your entire screenshot library once a night. It reads the recorded capture-version of each image, compares it to the current production release, and opens a tracked issue for any screenshot that is behind, with the version gap spelled out.
When to use it
Use it when screenshots accumulate faster than anyone can manually track. It turns silent drift into a visible, prioritized backlog so the docs team can regenerate the oldest images first.
How it works
- 1A nightly schedule triggers the run.
- 2The workflow lists every screenshot asset and its stored capture-version from the screenshot store.
- 3It fetches the latest production release tag from GitHub.
- 4A logic step computes which images were captured before the current minor release and ranks them by how far behind they are.
- 5For each stale image it creates a Linear issue tagged with the page, the captured version, and the target version.
- 6It posts a one-line Slack summary of how many screenshots fell out of date overnight.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
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.
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.
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.
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.
Research-driven localized hero banners tuned per market
An agent researches cultural and seasonal cues for each target market, adapts the master hero concept to fit local context, generates a tailored image per locale.
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.