DEVOPS
Publish GitLab Release Notes When a Trello Release Card Is Tagged Cut
When a card gets the "Cut Release" label, an agent assembles release notes from the milestone's merged MRs, creates the GitLab release against the tag.
How it runs
The automated pipeline, trigger to output.
- Trigger"Cut Release" label added to Trello cardTrello
- ActionPull milestone and merged MRs from GitLabGitLab
- LogicAgent drafts categorized release notes
- LogicConfirm version tag exists in GitLabGitLab
- ActionCreate GitLab release against the tagGitLab
- OutputPublish release notes page to ConfluenceConfluence
What it does
When an operator applies the "Cut Release" label to a release-train card, this kicks off an agent that reads the associated GitLab milestone, drafts human-readable release notes grouped by category from the merged MRs, creates the GitLab release tied to the version tag, and archives a copy of the notes in Confluence for the records.
When to use it
Use it at the moment of cutting a release when you want the GitLab release object and a stakeholder-friendly notes page generated together, without a release manager stitching together MR titles by hand.
How it works
- 1Adding the "Cut Release" label to a Trello card fires the trigger.
- 2The agent maps the card to its GitLab milestone and pulls all merged MRs.
- 3It categorizes changes (features, fixes, breaking) and drafts polished notes.
- 4A logic step verifies the version tag exists before publishing.
- 5The GitLab release is created against that tag with the generated notes.
- 6The same notes are published to a Confluence release page as the durable output.
Set it up
What you configure once, before turning it on.
- 1Connect TrelloKanban boards for everything.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.