ENGINEERING
Generate a third-party license attribution page in Confluence
On demand or on a schedule, collects every production dependency and its license from the lockfile.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run or scheduled trigger
- ActionFetch lockfile and filter to production dependenciesGitHub
- ActionResolve license and full license text per packageHTTP webhook
- LogicGroup by license and render attribution document
- OutputCreate or update the Confluence notices pageConfluence
What it does
Produces the open-source attribution document many products are legally required to ship. It reads the lockfile, resolves each production dependency's license and copyright text, groups packages by license type, and renders a clean, alphabetized notices page. It writes the result to a Confluence page, overwriting the previous version so the attribution always reflects the current dependency tree.
When to use it
Use it ahead of a release when you need an up-to-date NOTICES or third-party-licenses page, or on a recurring cadence to keep your published attributions accurate as dependencies change. It removes the manual, error-prone chore of assembling license text by hand.
How it works
- 1A manual run or scheduled trigger starts the generation.
- 2The flow fetches the lockfile and filters to production dependencies only.
- 3It resolves the SPDX license and full license text for each package.
- 4It groups packages by license and renders an alphabetized attribution document.
- 5It creates or updates the designated Confluence page with the rendered notices and a regeneration timestamp.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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 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.
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.
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.
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.