CONTENT CREATION
Merged PRs Since Last Tag to Deployed Changelog Microsite
When you push a new git tag, this collects every PR merged since the previous tag, rewrites the titles into human-toned release notes.
How it runs
The automated pipeline, trigger to output.
- TriggerNew git tag pushedGitHub
- ActionList PRs merged since previous tagGitHub
- LogicStop if no user-facing PRs in range
- ActionRewrite and group titles into prose changelogOpenAI
- ActionCommit changelog entry to content repoGitHub
- OutputDeploy updated microsite to VercelVercel
What it does
Turns a fresh release tag into a published, readable changelog page. It diffs the new tag against the previous one, gathers the merged pull requests in that range, groups them by type (features, fixes, chores), and rewrites the terse PR titles into prose a customer would actually understand. The result is built and deployed as a static microsite on Vercel.
When to use it
Use it when you cut releases by tagging and want a public-facing changelog without hand-writing one every sprint. Best for teams who already enforce decent PR titles and squash-merge.
How it works
- 1A new tag push fires the GitHub trigger.
- 2The flow resolves the previous tag and lists all PRs merged between the two refs.
- 3It checks whether any user-facing PRs exist; if the range is all internal chores, it stops without publishing.
- 4An LLM step rewrites and groups the titles into a dated changelog entry in friendly prose.
- 5The entry is committed to the changelog repo's content directory.
- 6Vercel builds and deploys the updated static site, and the live URL is returned.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect VercelDeploys, runtime logs, analytics.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.