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

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.