CONTENT CREATION
On Release Tag, Refresh All Doc Screenshots and Open a PR
When you publish a release tag, recaptures every documented screen from the newly deployed build, commits the regenerated images to a branch.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag publishedGitHub
- ActionCapture all documented screens on released buildBrowserbase
- LogicMark which screenshots changed
- ActionCommit updated images to a new branchGitHub
- OutputOpen consolidated review PRGitHub
What it does
Triggered by a published release tag, it recaptures the entire set of documented screens from the freshly deployed build, writes the updated images into the docs repo on a new branch, and opens one consolidated pull request. A human reviews the batch of regenerated screenshots in a single diff rather than hunting for stale images by hand.
When to use it
Use it when screenshots should be refreshed on a release cadence rather than per-commit, and you want a writer to approve the visual changes before they reach published docs. It pairs a deterministic capture pass with a human gate.
How it works
- 1A GitHub release tag is published, firing the trigger.
- 2Browserbase loads every screen in the docs manifest against the released build and captures each one.
- 3A compare step marks which images actually changed so unchanged files are left untouched.
- 4Changed images are committed to a fresh branch in the docs repository.
- 5A pull request is opened collecting all regenerated screenshots with a summary of which pages changed, ready for review.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 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.