SUMMARIZATION
Capture MR Architecture Decisions into a Confluence ADR
When an MR labeled architectural is merged, distills the design discussion in the thread into a structured Architecture Decision Record and publishes it to Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR merged eventGitLab
- LogicProceed only if MR has architecture label
- ActionFetch full MR discussion threadGitLab
- ActionStructure discussion into an ADROpenAI
- ActionPublish ADR page to ConfluenceConfluence
- OutputPost ADR link as note on the MRGitLab
What it does
This workflow watches for merged MRs tagged as architecturally significant, reads the design debate inside the thread, and distills it into a proper Architecture Decision Record: context, options considered, the decision, and consequences. It publishes the ADR to your Confluence space and drops a link back on the MR, turning ephemeral review chatter into durable documentation.
When to use it
Use it when meaningful design decisions get made in MR comments and then lost. It gives architecture-track teams an automatic ADR trail without anyone hand-writing one after the fact.
How it works
- 1GitLab MR merged event triggers the run.
- 2A logic step proceeds only if the MR carries the architecture label.
- 3The workflow fetches the full discussion thread.
- 4OpenAI structures the conversation into an ADR with context, considered options, decision, and consequences.
- 5The ADR is published as a new Confluence page in the decisions space.
- 6A note linking the ADR is posted on the merge record.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.