Customer Changelog Writer setup guide

What it does

Each GitHub release rewritten for customers, drafted in Notion and announced in Slack once your PM approves. Internal items dropped, nothing invented.

Checks your GitHub repository's releases (REST API, read-only token) on your plan's schedule interval.
AI rewrites each release for customers: benefit-first headline and bullets, who it's for and how to try it, dropping refactors, CI and chores and never inventing features.
Saves the entry as a Draft in your Notion changelog database for the PM to edit.
After the PM approves, reads the page back from Notion (so edits count), posts it to your Slack announcements channel with a newsletter blurb, and marks the page Announced.

What it needs

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.

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).

Availability and plans

Available

Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

A paid plan: agents run live, and the Free plan only runs Dry Runs.
An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
These apps, connected in Settings → Integrations: HTTP / Custom API, Notion and Slack.
The app it watches, connected in Settings → Integrations (the agent starts from an app event).
About 15 minutes.

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

Connect your AI provider

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).

Connecting HTTP / Custom API

3. Connect Notion

Connect Notion and share your changelog database with the Fluxo Flow integration (Settings → Integrations → Notion).

Connecting Notion

4. Connect Slack

Connect the Slack workspace announcements go to (Settings → Integrations → Slack).

Connecting Slack

5. Point the trigger at your releases

Open the trigger, pick the GitHub connection and enter the releases path.

Setting	What to enter	In step
GitHub connection (HTTP / Custom API)	An HTTP / Custom API connection with base URL https://api.github.com and a Bearer token that can read the repository's releases. Pick your connected HTTP / Custom API account.	“New GitHub release”
Releases path	The path of your repository's releases: /repos/<owner>/<repo>/releases.	“New GitHub release”

6. Describe your product

Open “Rewrite it for customers” and replace the placeholder with your product and changelog style.

Setting	What to enter	In step
Your product and changelog style	Replace the placeholder with your product, customers, plan names, tone, where customers find features, internal words never to use and whether to skip pre-releases. It starts as “[PASTE YOUR PRODUCT NAME, WHO YOUR CUSTOMERS ARE, YOUR PLAN NAMES, YOUR CHANGELOG TONE, HOW CUSTOMERS FIND NEW FEATURES (MENU PATHS, DOCS LINKS), WORDS YOU NEVER USE PUBLICLY (CODE NAMES) AND WHETHER TO SKIP PRE-RELEASES HERE]” until you replace it.	“Rewrite it for customers”

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).

Setting	What to enter	In step
Notion account	The Notion workspace with your changelog database. Pick your connected Notion account.	“Save the draft in Notion”
Changelog database	The Notion database entries are drafted in, with the properties Name (title), Status (select with the options Draft and Announced), Version (text), Release link (url).	“Save the draft in Notion”
Notion account (read back)	The same Notion account, to read the approved page. Pick your connected Notion account.	“Read the approved entry”
Notion account (mark Announced)	The same Notion account, to set Status to Announced. Pick your connected Notion account.	“Mark it Announced”

8. Pick the announcements channel

Open “Announce in Slack” and pick your account and channel.

Setting	What to enter	In step
Slack account	The Slack workspace announcements are posted to. Pick your connected Slack account.	“Announce in Slack”
Announcements channel	The channel your team (or customer community) reads, e.g. #announcements.	“Announce in Slack”

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.

Dry Run vs Run

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.

How it works

The agent is a normal workflow with 12 steps (2 AI steps, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.

New GitHub release — Starts on “New item at an endpoint” in HTTP / Custom API (an app event). Checks your repository's releases (GitHub REST API, with your token) on your plan's schedule interval and starts a run for each new release.
Rewrite it for customers — AI step (runs on your AI provider key). AI 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.
Anything for customers? — Decision: picks the branch to follow. Drafts, skipped pre-releases and internal-only releases aren't written up.
Not for customers — Kept in the run history. Branch: Internal only. Internal-only release, draft or skipped pre-release; the run history keeps the reason.
Save the draft in Notion — Notion: Create a page in a database. Branch: For customers. Adds the entry to your Notion changelog database with Status Draft, so the PM can edit it there.
PM approves the entry — A person approves or rejects it in Reviews (the run waits). The PM opens the Draft page in Notion, edits it there if needed and approves in Reviews. Nothing is announced before that.
Left as Draft — Kept in the run history. Branch: Rejected. Not announced; the Notion page stays a Draft.
Read the approved entry — Notion: Read a page's text. Branch: Approved. Reads the page's text back from Notion, including the PM's edits.
Format the announcement — AI step (runs on your AI provider key). AI formats the approved page for Slack and pulls out the newsletter blurb — rewording nothing and adding nothing.
Announce in Slack — Slack: Post a message. Posts the approved entry to your announcements channel, with the newsletter blurb in the thread-ready line below.
Mark it Announced — Notion: Update page properties. Sets the Notion page's Status to Announced.
Announced — Kept in the run history. The run history keeps the release, the approved text and the Slack message.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.

Sample data fields

name, id, tag_name, published_at, draft, prerelease, html_url, body.

Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.

Go live

Open the trigger and click “Activate app trigger”: releases are checked on your plan's schedule interval. Releases published before activation are skipped.
Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

Questions

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).

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 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.

Troubleshooting

“No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
A run shows as paused: it's waiting for someone in Reviews to approve or reject it.
A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

Generated from the agent's own workflow, so it always matches what the agent does. Last updated October 12, 2026.