DOCUMENT OPS
Release-tag doc coverage report to Confluence
When you publish a GitHub release, it builds a documentation coverage report for that version — which new endpoints shipped documented vs. undocumented — and publishes it…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- ActionCompute endpoint delta since previous tagGitHub
- ActionFetch documented surface from ReadMeReadMe
- LogicClassify coverage and score the release
- OutputPublish coverage report to ConfluenceConfluence
What it does
Produces an auditable per-release documentation coverage record. On each tagged release it diffs the API surface introduced since the previous tag against what ReadMe documents, then writes a stakeholder-friendly Confluence page summarizing what shipped with docs and what didn't.
When to use it
Use it when release governance or compliance requires evidence that shipped features were documented, or when product and support need a per-version reference of doc completeness. Tie it to your release process so the report is always current with the latest tag.
How it works
- 1A GitHub release published event triggers the workflow.
- 2It computes the endpoints added or changed between the previous tag and this release.
- 3It fetches the documented surface from ReadMe and matches it against the release delta.
- 4A logic step classifies each new endpoint as documented, partially documented, or missing, and calculates an overall coverage score.
- 5It publishes a formatted coverage report as a Confluence page under the release space, linked from the release notes.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ReadMeAPI docs, changelog, auth.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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 Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.