456
Workflow

Changelog to Newsletter Automation

Turn shipped-feature notes into a monthly customer newsletter.

1 min readupdated 2026-07-04

/ quick answer

Aggregate Linear/GitHub releases, group by theme, rewrite for customers, and send. Turn shipped-feature notes into a monthly customer newsletter.

Turn shipped-feature notes into a monthly customer newsletter. The problem it solves: Product ships weekly but customers only hear about half of it. Aggregate Linear/GitHub releases, group by theme, rewrite for customers, and send. It runs in 5 steps, starting with pull closed issues tagged 'shipped' from linear/github for the period. This workflow node is part of the Onexial knowledge graph and links to related concepts, workflows and tools below.
Problem
Product ships weekly but customers only hear about half of it.
Solution
Aggregate Linear/GitHub releases, group by theme, rewrite for customers, and send.
Steps
  1. 01Pull closed issues tagged 'shipped' from Linear/GitHub for the period.
  2. 02Cluster by theme (UX, performance, integrations).
  3. 03Rewrite each cluster in customer-benefit language.
  4. 04Add screenshots and GIFs where available.
  5. 05Ship via Beehiiv or Customer.io on the first of the month.
Tools Used
Related Dictionary
/ frequently asked

What does the Changelog to Newsletter Automation workflow do?

Aggregate Linear/GitHub releases, group by theme, rewrite for customers, and send.

What problem does Changelog to Newsletter Automation solve?

Product ships weekly but customers only hear about half of it.

How many steps does Changelog to Newsletter Automation take?

5 steps. It starts with pull closed issues tagged 'shipped' from linear/github for the period. and ends with ship via beehiiv or customer.io on the first of the month..

Which tools does Changelog to Newsletter Automation need?

It uses newsletter-automation-stack — each linked below with its own node.

/ tools we use for this

Some links support Onexial at no extra cost to you.