CONTENT CREATION
Auto-fill alt-text for screenshots in docs pull requests
When a docs pull request adds screenshot images, generates localized alt-text for each, commits it into the referencing Markdown, and comments a coverage report on the PR.
How it runs
The automated pipeline, trigger to output.
- TriggerDocs PR adds screenshot imagesGitHub
- ActionFetch added images and referencing MarkdownGitHub
- LogicSkip images that already have alt-text
- ActionGenerate localized alt-text per imageOpenAI
- ActionCommit alt-text into files on PR branchGitHub
- OutputComment coverage report on the PRGitHub
What it does
Scans documentation pull requests for newly added screenshot images, generates accessibility alt-text in your default and translated locales, and writes that alt-text into the Markdown or MDX that references each image. It then posts a comment on the PR summarizing which images were described and flags any it couldn't read.
When to use it
Use it on docs and help-center repos where contributors paste screenshots without alt-text and reviewers keep catching it. It enforces accessibility coverage as a PR step so localized docs ship compliant without a manual editorial pass.
How it works
- 1A pull request touching image files in the docs repo triggers the flow.
- 2The flow fetches the added screenshots and the Markdown that references them from GitHub.
- 3A logic step skips images that already have non-empty alt-text.
- 4OpenAI reads each image and produces alt-text in the default and target locales.
- 5The flow commits the updated alt-text into the referencing files on the PR branch.
- 6A coverage comment listing described and skipped images is posted to the pull request.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 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
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.