# Customer-facing changelog from merged PRs

Merged pull requests are collected, grouped, and turned into a plain-language changelog draft for customers. A person edits before it is published and emailed.

**Why it matters:** Shipping is marketing, but engineers write PR titles for engineers. This turns them into updates customers understand.

- Trigger: PRs merged / release tagged
- Tools: GitHub, n8n, OpenAI, Gmail
- Time saved (rough estimate): 1–3 hours/week
- Typical agency build cost (rough estimate): $800–$2.5k

## Steps
1. Fetch merged PRs + labels
2. Drop internal-only changes
3. Write customer-facing notes
4. PM edits
5. Publish + email

## Pitfalls
- Label PRs (customer-facing or internal) or the model will leak internal details.

## Sources
- [n8n community template #18981: Draft customer-facing changelogs from merged GitHub PRs](https://n8n.io/workflows/18981/)
- [Zapier: how Zapier uses AI internally](https://zapier.com/blog/how-zapier-uses-ai/)

---
Source: https://cofounderbase.com/workflows/changelog-from-merged-prs/?utm_source=md&utm_medium=ai · Cofounderbase, a directory of agencies that build AI internal tools and automations. Data comes from each agency's own website and official partner directories; rankings are not sold.
