ENGINEERING
Recorded design sync to Confluence ADR draft
When a Zoom design-sync recording finishes, transcribe it, extract the architectural decision plus its context, options, and consequences, and publish a structured ADR draft page…
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completed for design-sync meetingZoom
- ActionFetch meeting transcript from ZoomZoom
- ActionExtract decision, context, options, consequencesOpenAI
- LogicSkip if no decision was actually reached
- OutputPublish Proposed ADR draft to Confluence spaceConfluence
What it does
Turns a recorded architecture-review call into a ready-to-edit Architecture Decision Record. It pulls the meeting transcript from Zoom, identifies the single decision the team converged on, and writes a Confluence page following the standard ADR template (Context, Decision, Options Considered, Consequences) so nobody has to reconstruct the discussion from memory.
When to use it
Use it when your team makes architectural calls in recorded Zoom syncs but consistently fails to document them afterward. Best for squads that already keep ADRs in a Confluence space and want the first draft generated within minutes of the call ending.
How it works
- 1A Zoom recording-completed event fires for a tagged design-sync meeting.
- 2Fetch the recording's transcript via the Zoom API.
- 3An LLM extracts the decision, surrounding context, alternatives weighed, and trade-offs accepted.
- 4A logic check confirms a real decision was reached; ambient discussions with no resolution are skipped.
- 5Create a Confluence page in the ADR space, status "Proposed," pre-filled from the extracted fields and linked to the recording.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 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 Engineering workflows
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…
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.
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.
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.
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.
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.