We're excited to introduce a new Automation that allows you to configure automated periodic recaps for your products. A "periodic recap" is just a customer update we write on a regular cadence — every day, every week, or every month — based on the frequency you pick. Think of it as a short, regular summary of what's changed that you can send to customers automatically.
This feature makes it easier than ever to keep your customers informed. The system automatically collects data such as merged pull requests, notable commits, and tickets to generate a polished update.
Where the recap goes is up to you. You can send it to your inbox for review first, or publish it directly to any destination — Slack, Discord, your hosted Changelog, or anywhere else you communicate with customers.
Example: Send a private Slack message to customer-success once a month for manual review.
Example: Publish weekly recaps straight to your hosted Changelog without manual steps.
Example: Deliver daily summaries to a channel in Discord for an internal engineering channel.
Setting up these recaps is simple. This is an additional Automation available in the automation form — choose the 'Periodic Recap' option when creating or editing an automation, select the product, and pick the desired cadence. You can add it alongside other automations for the same product.
We’re sharing a set of bug fixes this week that clear up confusing behavior and styling issues across the product.
Bug fixes
Password reset page: The page was mis-styled and the submit button wasn’t visible — that’s fixed. The page now uses the current two-column layout, the form styling is corrected, and the submit button appears as expected.
Publication display date: The changelog and feeds could show the wrong relative time (for example, “12 hours ago” after you’d just published) when using the Kitty template because a helper calculated the date at midnight. We now store and display the full datetime so the published time in the changelog, feeds, and API reflects the actual moment of publication.
Confusing publish button: The “Publish to more...” button on already-published updates while viewing the "Publications" tab would do nothing, and on other tabs would simply navigate to the "Publications" tab. We removed it.
Publish button in Recap and Spotlight wizards: On the publish screen in the Recap or Spotlight wizard the publish button could stay disabled even when destinations were pre-selected. It’s now enabled correctly unless there are no destinations selected.
Live chat streaming: Fixed an issue where streamed chat messages could appear garbled as they arrived. Replies now render cleanly during streaming.
Auto-growing chat input: The AI chat input in the Customer Update editor was a tiny, fixed single row, which made it hard to see your message if you had a lot to say. It now expands vertically as you type, growing upward from the input area, and resets to a single row after sending a message.
Preset chat commands in Recap builder: Preset chat commands didn’t work in the Recap builder — they now trigger correctly.
Animated GIF uploads: Newly uploaded animated GIFs were appearing as single frames. They now are properly animated.
Customer Update editor layout: On some pages the Customer Update editor wouldn’t use all the vertical space available. It now fills the available vertical space for a better editing experience.
Automatically convert code changes into clear, on-brand updates. With Automations, you can define when updates are generated and where they’re sent, keeping customers informed with minimal effort. It drafts, previews, and routes update notes from your commit activity so your team can focus on shipping.
Why you'll like it
Save time — reduce the manual work of drafting and publishing update notes.
Stay consistent — generated updates follow your style and can be previewed before sending.
Keep control — set flows to draft for review or auto-publish once they meet your criteria.
Send updates where they belong — to the Inbox for review, or to any destinations, like Slack, Discord, or your hosted changelog.
We’ve removed the old Experimental settings pages — Automations replaces them with a more robust, user-friendly experience. To get started, open Automations in the sidebar and create your first rule. We'll be following up very soon with additional Automation sources like a daily recap generator and a development activity feed generator.
You can now publish your customer updates to Discord, alongside other destinations like Slack. Add Discord as a destination to get started.
A customer update published to a Discord channel
Other highlights
Brand icons now appear across publication views so you can scan destinations at a glance.
Destination and integration dropdowns are now alphabetized.
“Webflow Integration” is now labeled “Webflow Site.”
Give it a try — add a Discord destination and publish something. If anything acts up, let us know and we’ll sort it out.
You've just generated and refined the customer update for your brand new feature and published it to your changelog and widget — but now you want to post about it on X.com too.
That's where Editions come in: generate an X-ready version, tweak it in the editor, then copy and paste to post.
What Editions does
Generate channel-specific variants (X, LinkedIn, etc.) with appropriate tone, length, and formatting.
Let you edit any generated variant in a simple editor.
Provide AI suggestions and a chat-based refinement option to iterate on wording.
Support undo/redo while you edit.
How you use it
Create a Customer Update.
Choose which channels you want editions for.
Generate editions and review AI suggestions.
Edit or refine each edition, then publish the versions you need.
Publishing for now
Currently Editions generates the text for each channel; you'll need to copy and paste the generated version into the target platform to publish. Direct publishing integrations with X.com and LinkedIn are coming shortly.
