Weekly Linear changelog to a customer email, Notion, and Slack

Every Friday at 4pm, turn this week's shipped Linear work into a plain-English customer changelog, publish it in Notion, email your subscribers, and post a heads-up in Slack.

Agentic Task
LinearAI GenerationNotionResendSlackProductMarketingContent GenerationEmail AutomationAI Reports

Every Friday at 4pm in my timezone, I want an agent to turn this week's shipped Linear work into a customer-facing release notes email, a permanent changelog page in Notion, and a one-line heads-up in my product Slack channel. The trigger is a weekly cron.

Step 1. Pull the source material from Linear. Use Linear's List Issues to fetch every issue that was completed in the last 7 days from the teams and projects I designate (I will tell you which ones during setup). Filter to issues whose state moved to a completed status in that window. Include the title, description, labels, project, team, assignee, and the Linear URL for each issue so I have everything I need to write about them.

Step 2. Use AI Generation (Generate Completion) to do the actual judgment work. This is the whole point of using an agent. The model should:

- Drop anything internal-only: chores, refactors, dependency bumps, infra cleanup, dark-launched flags, anything labeled internal or with a project that is not customer-facing.

- Group related issues together so a customer reads one bullet per change, not five duplicate bullets for the same feature shipped across several tickets.

- Translate dev-language titles and descriptions into customer-benefit framing: what the user can now do, what got faster or clearer, what bug they were hitting that is now fixed. Strip implementation detail.

- Organize the output into three sections in this order: New (net-new features), Improved (existing flows that got better), and Fixed (bugs resolved). Skip a section entirely if there is nothing for it.

- Match my brand voice. I will provide a short style note and a sample changelog from a past week; follow that tone, length per bullet, and the level of detail I usually share. No em dashes.

- Write a short intro paragraph (2 to 3 sentences) for the email and a 4 to 8 word subject line that names the most exciting change of the week.

Step 3. Publish the polished changelog as a new page in my Notion changelog database using Create a Page. The page title is the date range (for example, "Changelog: June 2 to June 6"), and the body is the formatted New, Improved, Fixed content. Capture the URL of the new Notion page so we can link to it from the email and Slack post.

Step 4. Send the customer email through Resend's Send Email to the changelog subscriber list I designate. Body is the intro paragraph plus the New, Improved, Fixed sections, plus a "read the full changelog" link to the Notion page. Subject line comes from step 2. Use my verified sender.

Step 5. Post a one-line heads-up to the #product Slack channel using Slack's Send a Message, with the subject line and a link to the Notion page so the team knows the changelog went out.

Edge cases. If nothing customer-facing was completed this week, skip the Notion page and the email and post a short "nothing customer-facing shipped this week" note in Slack so I know the run finished cleanly. If only one section has entries, still send the email but only render that section.

Setup inputs I will provide: Linear team and project IDs to include, the Notion changelog database ID, the Resend audience or recipient list and verified sender address, the Slack channel name, my timezone, and a short style note with one sample changelog in my voice.

Additional information

What does this prompt do?
  • Pulls the issues your team marked done in Linear over the last seven days from the teams and projects you choose.
  • Translates dev-language titles and descriptions into customer-benefit language, then groups them into New, Improved, and Fixed sections.
  • Drops anything internal-only like refactors, chores, and dark-launched flags so subscribers only see what changed for them.
  • Publishes the polished changelog as a new page in your Notion changelog database and emails it to your subscriber list through Resend.
  • Posts a short heads-up in your product Slack channel with a link to the Notion page so the team knows the changelog went out.
What do I need to use this?
  • A Linear workspace, plus the names of the teams or projects whose completed work belongs in your customer changelog.
  • A Notion workspace with a changelog database you want each weekly entry created in.
  • A Resend account with a verified sender domain and an audience or subscriber list to email.
  • A Slack workspace and the channel where you want the weekly heads-up posted.
  • A short style note about your voice, your product name, and anything you never want mentioned to customers.
How can I customize it?
  • Change the schedule. Run it Friday at 4pm, Monday morning, or end of sprint, whatever cadence matches your release rhythm.
  • Pick which Linear teams or projects count. Only ship-worthy work from those scopes makes the changelog; everything else is ignored.
  • Tune the voice. Give it a sample paragraph in your brand tone and it will match length, formality, and the kinds of details you do or do not call out.
  • Swap or add destinations. Skip the email if you only want a Notion page, send to a different list per product, or replace Slack with Microsoft Teams.

Frequently asked questions

How is this different from a GitHub-based changelog?
Linear is the product manager's curated view of what actually shipped, not every merged pull request. The output reads like a release update, not a code diff, because chores, refactors, and internal-only work are filtered out before anything is written.
Will it write in our voice?
Yes. You give it a short style guide or a sample of a past update and it matches your tone, length, and the kind of detail you usually share. You can tweak the style note any time and the next run will follow it.
Can I review the email before it goes out?
Yes. You can have it create a draft in Notion and a draft email in Resend and pause until you approve, or send the Slack heads-up only after you mark the Notion page as published.
What if we did not ship anything this week?
If nothing customer-facing was completed, it skips the email and the Notion page and posts a short note in Slack so you know the run finished cleanly with nothing to share.
Can I use a different email tool or a different doc tool?
Yes. Resend can be swapped for another email sender and Notion can be swapped for a different docs tool. The judgment work, deciding what is changelog-worthy and how to phrase it, stays the same.

Stop hand-writing release notes every Friday.

Connect Linear, Notion, Resend, and Slack once, and Geni turns every week's shipped work into a customer-ready changelog for you.