CONTENT CREATION
Flag Stale Doc Screenshots on Every UI Pull Request
When a PR changes front-end UI files, this workflow cross-references which docs screenshots depend on those components and posts a checklist comment listing the images…
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or updatedGitHub
- LogicFilter to UI component file changes
- ActionLoad component-to-screenshot mapNotion
- LogicResolve affected screenshots; exit if none
- OutputPost screenshot checklist as PR commentGitHub
What it does
Every time a pull request touches UI code, this workflow figures out which documentation screenshots are now at risk of being out of date and posts a review comment naming each one, so reviewers never merge a UI change that silently breaks the docs.
When to use it
Use it when your docs live alongside code and screenshots tend to rot after redesigns. Ideal for teams who want screenshot freshness enforced as part of code review instead of discovered by an angry customer weeks later.
How it works
- 1A GitHub pull request event fires when files change.
- 2The workflow inspects the changed file paths and keeps only the ones under your UI component directories.
- 3It loads a mapping (kept in a Notion database) of components to the doc screenshots that show them.
- 4A logic step resolves the changed components to the set of affected screenshot files.
- 5If the set is empty it exits quietly; otherwise it posts a GitHub PR comment with a checkbox list of every screenshot to re-capture and the page each appears on.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
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.
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.
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.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
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.
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.