Skip to content

Customer Changelog Writer · SaaS & Startups

Release notes your customers will actually read, every release

Each GitHub release rewritten for customers with a benefit-first headline and plain bullets, drafted in Notion and announced in Slack once your PM approves. Nothing invented.

Available now $79 one-time · never renewsIncluded in Enterprise

Free account to start. Buying and running live need a paid plan.

  • Starts from an event in a connected app
  • 2 AI steps
  • A person approves before it acts
  • About 15 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Our release notes are full of ticket numbers and refactors customers don't care about.”
  • “We ship great features and nobody outside engineering hears about them.”
  • “Writing the public changelog is always the last thing anyone wants to do on release day.”

What you get with the agent

  • Every new GitHub release picked up with a read-only token.
  • A benefit-first headline, plain-language bullets, who it's for and how to try it.
  • Internal items like refactors, CI, dependency bumps and chores dropped, and no feature or benefit invented.
  • A draft in your Notion changelog database for the PM to edit and approve.
  • The approved text, PM edits included, posted to your Slack announcements channel with a newsletter blurb.

Before

The release ships Friday. The changelog says v4.12.0, fix #2252, bump deps, and marketing asks on Monday what actually changed.

After

Within the hour, Notion has a draft headlined Send invoices in more currencies. The PM tweaks a bullet, approves, and Slack has the announcement plus a newsletter blurb.

How it works

The whole workflow, step by step.

The agent checks your repository's GitHub releases with a read-only token. For each new release, AI rewrites it for customers: a benefit-first headline, plain-language bullets, who it's for and how to try it. It drops internal items (refactors, CI, dependency bumps, chores) and never invents a feature or benefit the notes don't state. The entry is saved as a Draft in your Notion changelog database, where the PM edits it. After approval the agent reads the page back from Notion, so the PM's edits count, posts it to your Slack announcements channel with a newsletter blurb, and marks the page Announced. One repository per setup. It doesn't publish to your website or newsletter tool.

  1. TriggerNew GitHub release
  2. AI stepRewrite it for customers
  3. LogicAnything for customers?
    • Internal only:Not for customers
    • For customers:Save the draft in Notion
  4. OutputNot for customers
  5. App callSave the draft in Notion
  6. Human approvalPM approves the entry
    • Approved:Read the approved entry
    • Rejected:Left as Draft
  7. OutputLeft as Draft
  8. App callRead the approved entry
  9. AI stepFormat the announcement
  10. App callAnnounce in Slack
  11. App callMark it Announced
  12. OutputAnnounced

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1New GitHub releaseChecks your repository's releases (GitHub REST API, with your token) on your plan's schedule interval and starts a run for each new release.
  2. Step 2Rewrite it for customersAI turns the release notes into a customer changelog entry (headline, benefit-first bullets, who it's for, how to try it) and drops internal items like refactors, CI and chores.
  3. Step 3Anything for customers?Drafts, skipped pre-releases and internal-only releases aren't written up.
  4. Step 4Not for customersInternal-only release, draft or skipped pre-release; the run history keeps the reason.
  5. Step 5Save the draft in NotionAdds the entry to your Notion changelog database with Status Draft, so the PM can edit it there.
  6. Step 6PM approves the entryThe PM opens the Draft page in Notion, edits it there if needed and approves in Reviews. Nothing is announced before that.
  7. Step 7Left as DraftNot announced; the Notion page stays a Draft.
  8. Step 8Read the approved entryReads the page's text back from Notion, including the PM's edits.
  9. Step 9Format the announcementAI formats the approved page for Slack and pulls out the newsletter blurb — rewording nothing and adding nothing.
  10. Step 10Announce in SlackPosts the approved entry to your announcements channel, with the newsletter blurb in the thread-ready line below.
  11. Step 11Mark it AnnouncedSets the Notion page's Status to Announced.
  12. Step 12AnnouncedThe run history keeps the release, the approved text and the Slack message.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

GitHub release v4.12.0 for Acme Ledger: support for 12 more currencies on invoices, auto-categorizing recurring bank transactions, a PDF export fix, internal dependency bumps.

The agent produces

Draft: Invoice clients in their own currency. Bullets on new currencies, smarter bank categorization and a fix for cut-off client names on PDFs; dependency bumps dropped. Who it's for and how to try it. Saved as a Draft in Notion; announced in Slack after PM approval.

What you need

Everything it takes to run it.

About 15 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $79 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • A GitHub token as an HTTP / Custom API connection (https://api.github.com), plus Notion and Slack.
  • Release notes on GitHub Releases.

Setup, about 15 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect GitHub (HTTP / Custom API). Add an HTTP / Custom API connection: base URL https://api.github.com, Bearer token = a read-only GitHub token (Settings → Integrations → HTTP / Custom API).
  3. Connect Notion. Connect Notion and share your changelog database with the Fluxo Flow integration (Settings → Integrations → Notion).
  4. Connect Slack. Connect the Slack workspace announcements go to (Settings → Integrations → Slack).
  5. Point the trigger at your releases. Open the trigger, pick the GitHub connection and enter the releases path.
  6. Describe your product. Open “Rewrite it for customers” and replace the placeholder with your product and changelog style.
  7. Pick the changelog database. Open “Save the draft in Notion”, “Read the approved entry” and “Mark it Announced” and pick your Notion account (and the database in the first).
  8. Pick the announcements channel. Open “Announce in Slack” and pick your account and channel.
  9. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  10. Switch the trigger on. Open the trigger and click “Activate app trigger”: releases are checked on your plan's schedule interval. Releases published before activation are skipped.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • SaaS product managers
  • Startup founders shipping weekly
  • Product marketing and developer relations teams

What it doesn't do

  • It never invents features or benefits: only what the release notes say, and the PM approves every entry.
  • One repository per setup. It doesn't publish to your website or newsletter tool.
  • Not Deploy Manager (internal release notes and deploy gate) or Vendor Release Watch (other vendors' releases).

We list the limits up front so you can decide before you buy.

Price

$79 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Customer Changelog Writer.

Will it make features up?

No. It only describes what the release notes say, drops what it can't explain safely, and the PM approves every entry before it's announced.

Does it publish to our website?

No. It drafts in Notion and announces in Slack; copy the newsletter blurb into your newsletter tool. It covers one repository per setup.

What do I need?

A read-only GitHub token saved as an HTTP connection, release notes on GitHub Releases, Notion and Slack. Setup takes about 15 minutes.

Is it worth the price?

A one-time price that never renews, against rewriting every release by hand. Live runs need a paid plan and your own AI provider key; Dry Run is free.

Which token do I need?

A GitHub fine-grained token with read-only access to the repository's contents (releases). Add it as a Bearer token on the HTTP / Custom API connection (base URL https://api.github.com).

Does it publish to my website?

No. It drafts in Notion and announces in Slack; copy the newsletter blurb into your newsletter tool.

What Notion database do I need?

A database with the properties Name (title), Status (select with the options Draft and Announced), Version (text), Release link (url), shared with the Fluxo Flow integration.

Is this a subscription?

No. Customer Changelog Writer is a one-time purchase of $79 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Customer Changelog Writer to work.

Free account, no credit card. Your Agents page opens with Customer Changelog Writer ready to buy and set up, then Dry Run it before it goes live.