Release notes are tedious. You know what shipped, but turning Linear tickets into a polished document means clicking through issues, checking statuses, and formatting everything nicely in Notion. It's the kind of work that takes 30 minutes but feels like it should take 5.
With Linear and Notion connected, Claude can do the whole thing: pull recently completed issues, organize them by feature area, and create a formatted page ready to share with your team or customers.
Claude, write release notes in Notion based on our recent progress from Linear
Claude needs access to both Linear (to see what's been completed) and Notion (to create the release notes page). Once connected, it can pull issue data, check statuses, and write directly to your workspace.
Connect your Linear workspace and Notion account. Claude will read from Linear and write to Notion—you'll see exactly which tools it's using as it works.
Turn on Research mode to let Claude explore your Linear workspace more thoroughly—checking multiple projects, looking at issue labels, and gathering context about what each feature does.
Claude gathers your completed issues, organizes them into categories, and creates a formatted Notion page with everything stakeholders need to know.
I'll help you create release notes in Notion based on your recent Linear progress. Let me start by gathering information from your Linear workspace to see what's been completed recently.
I found 12 completed issues from the past week across three main feature areas. I've created your release notes page in Notion with the following structure:
Release Notes - Week of December 9
The release notes include professional formatting with clear sections, a summary of completed vs. in-progress work, and statistics showing 9 issues completed with 3 in progress.
You can access the page here: https://www.notion/releasenotes
The release notes provide a comprehensive overview that would be perfect for sharing with stakeholders, team members, or customers to communicate the significant progress made across these three major feature areas.
Adjust the structure, add sections, or change how features are grouped based on your team's preferences.
Can you reorganize this by team instead of feature area? And add a section at the top with key metrics—how many issues closed, average cycle time, that kind of thing.
Generate a separate version written for external audiences, focusing on benefits rather than technical details.
Now create a customer-facing version. Skip the internal bug fixes and technical details—focus on what users will actually notice and care about.
Turn this into a repeatable process that runs at the end of each sprint or release cycle.
This worked great. Can you save this as a workflow I can run every two weeks at the end of our sprint? Same format, same Notion location.
Notice the example prompt is just one sentence. When Claude has access to your actual data through Linear and Notion, you don't need to explain what a release note should look like—Claude can see your issues and write appropriately.
For teams with multiple projects or complex label structures, Research mode lets Claude explore more thoroughly before writing. It might check issue labels, project groupings, and recent activity to create better-organized notes.
Claude shows you which Linear queries it's running (list_issues, list_issue_statuses). If the results aren't what you expected, you can refine your request—"focus on the mobile project" or "only issues closed this week."
Claude creates a real Notion page, not a preview. You can edit it, share it, or move it to a different location in your workspace. It's your document now.