Workflow overview
Why this workflow matters
Useful for software delivery and engineering operations. Relevant for managed services and support workflows.
📝 Release Note Helper Triggered by a GitLab MR webhook, this workflow automatically assists your team in writing customer-facing release notes by combining Linear issue data with Claude AI. Apply the rn-release-AlekSystem label to any release note MR in your docs repository to trigger it. How it works Version detection — reads your release RSS feed to find the last published version, then fetches all matching Linear version labels created since then to determine the version range automatically Issue collection — queries Linear for all completed issues in that version range that have Zendesk tickets, Slack links, or custom labels (Customer request, Release note public) attached Ticket summary — posts a structured list of all relevant issues to the MR as a comment AI draft — sends issue details to Claude, which generates customer-facing changelog entries grouped into ### Enhancements and ### Fixes, posted as a second MR comment Done label — adds rn-done to the MR when complete to prevent re-runs Setup Configure a GitLab webhook on your docs repo pointing to this workflow's URL (Merge Request events) Create two labels on your GitLab repo: rn-release-AlekSystem (to trigger) and rn-done (auto-applied on completion) Update the RSS Read node URL to your release RSS feed Replace YOUR_PROJECT_ID in all GitLab API nodes with your docs project ID Replace YOUR_WORKSPACE in the Code nodes with your Linear workspace slug Connect Linear API, GitLab API, and Anthropic API credentials Notes Versioning assumes a vX.Y Linear label convention — adapt the Format labels node for your own scheme The AI prompt in Message a model is ready to use but can be customised to match your tone and changelog format Issues are filtered to those with Zendesk, Slack attachments, or your custom labels — adjust in Set Params
Best fit
Categories
Services
Use cases
Need another direction?