CONTENT CREATION
Frontend PR Docs Screenshot Impact Flagger
When a frontend PR merges, it maps the changed UI routes to docs pages that screenshot those screens and posts a checklist comment on the PR flagging which doc images likely need…
How it runs
The automated pipeline, trigger to output.
- TriggerFrontend PR merged on GitHubGitHub
- ActionFetch changed files and resolve to UI routesGitHub
- LogicMatch routes to docs pages and exit if none
- OutputComment impacted screenshot checklist on the PRGitHub
What it does
Turns every merged frontend PR into a docs-screenshot heads-up. It inspects which UI components or routes the PR touched, looks up which published doc pages screenshot those exact screens, and comments back on the PR with a checklist of images that probably went stale.
When to use it
Use it when UI changes routinely ship without anyone updating the corresponding docs screenshots. Catching the impact at merge time, while the change is fresh in the author's mind, is far cheaper than discovering drift weeks later.
How it works
- 1A GitHub pull-request merged event triggers the flow.
- 2The flow pulls the PR's changed files and resolves them to affected UI routes.
- 3A logic step cross-references a route-to-doc mapping to find doc pages whose screenshots cover those routes.
- 4If no docs reference the changed routes, the flow exits quietly.
- 5Otherwise it posts a comment back on the PR with a checklist of doc images to re-capture, each linked to its source page.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.