ENGINEERING
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
How it runs
The automated pipeline, trigger to output.
- TriggerSemver release tag pushedGitHub
- ActionPull spec at new + previous tagGitHub
- LogicClassify changes into changelog sections
- ActionRender Confluence changelog body
- OutputPublish versioned page to ConfluenceConfluence
What it does
Turns each tagged API release into a permanent, readable changelog entry in Confluence. It collects every spec change since the prior tag, groups them into Breaking, Added, and Fixed, and publishes a new child page under your API docs space with the version, date, and migration guidance.
When to use it
Your platform team cuts versioned API releases and downstream teams keep asking "what changed in v2.4?" Use this to make the answer self-serve and authoritative instead of buried in commit history.
How it works
- 1A release tag matching `v*.*.*` is pushed, triggering the flow.
- 2Pull the commit range and the OpenAPI spec at both the new tag and the previous tag from GitHub.
- 3Diff the specs and classify each change into Breaking / Added / Fixed buckets.
- 4Render a Confluence-formatted changelog body with the version header and migration notes.
- 5Create the page as a child of the API docs parent page in Confluence.
- 6Link the published page back on the GitHub release notes.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.