How it works
What this workflow does
Turn a spoken release recap into a Webflow release-notes draft. The editor opens a private n8n form, dictates the recap, reviews it, and supplies the confirmed list of shipped changes. The workflow validates the input, drafts a summary and one changelog entry with change headings, and creates a staged Webflow CMS item.
The workflow imports inactive with dryRun: true. Run with sample data uses a fictional checklist update, so the preview does not call OpenAI, Webflow, or the Data Table.
This is the release-notes layer for the Content Publishing, Social Distribution & Newsletter Intelligence blueprint; the Project Delivery QA & Completion blueprint covers the shipped work behind the notes.
The private form
Receive event is an n8n Form Trigger protected by Basic Auth. Editors get fields for Draft ID, Release name or version, an optional Release date (YYYY-MM-DD), Audience, Dictated product recap, and Verified shipped changes. The release name must be one line, and the draft ID must be stable and lowercase.
The release date is validated as a real calendar date or omitted when blank. A live run also requires a Data Table, model, 24-character Webflow collection ID, and valid distinct CMS field slugs.
Only shipped changes become notes
OpenAI returns a summary, an introduction, and one to six changes. Each change needs a short label, a description, and an exact evidence quote from the verified shipped changes. The workflow rejects unsupported changes, invented quotes, and oversized fields.
Any number in the copy must appear in the release name or the verified shipped changes. The optional release date is added as a paragraph only when supplied. The workflow escapes the content and creates a staged Webflow item with isDraft: true, verifying the returned item ID, draft state, archive state, and slug before recording draft_ready. It never publishes.
Replays and validation scope
The Data Table is keyed by the draft ID. An existing request stops the run and preserves the current review state. A new request is reserved as draft_pending before the Webflow call.
The supplied report confirms the isolated n8n 2.47.4 import, inactive state, the built-in sample, and a local copy of the native form. It also covers blank and impossible release dates, shipped-change evidence, and staged-only Webflow behavior. Live Wispr Flow dictation, deployed forms, credentials, model responses, and Webflow or Sheets operations require staging.
How to use
Before you start
- A current n8n instance with Form Trigger and Data Table support.
- A Webflow account, site, and changelog collection.
- A Webflow API token with
cms:write. - An OpenAI API key and a JSON-mode model.
- Wispr Flow configured for the editors who will dictate.
- The confirmed list of shipped changes.
1. Import and run the sample
Download the complete package, extract the ZIP, and read the full setup guide. Import voice-to-webflow-release-notes.n8n.json and keep it inactive.
Open Run with sample data and choose Test workflow. Assemble release notes draft should return a summary, introduction, and the sourced change headings.
2. Prepare the private form and state table
Select a Basic Auth credential on Receive event. Start the form test and open the Test URL. Dictate the recap with Wispr Flow, review the text, and submit.
Create an n8n Data Table with text columns event_key, status, detail, and result_id. Enter its ID in Setup together with the Webflow collection ID, model, and brand voice.
3. Configure Webflow fields
Set bodyField to the Rich Text field slug and summaryField to the Plain Text summary slug, or clear the summary field. Configure any other required fields before staging. Select a Webflow Header Auth credential on Create Webflow CMS draft with cms:write, and add an OpenAI Header Auth credential on Draft with OpenAI.
4. Test and operate
Enter a release name or version and a release date in YYYY-MM-DD format, or leave the date blank. A blank date is omitted; an invalid date fails before drafting. Dictate the recap and paste only confirmed shipped changes into their own field.
A change outside the shipped list fails the evidence check. Confirm availability and rollout scope in the CMS before publishing; for staged rollouts, describe only the audiences included in the supplied facts.
If draft_pending remains, look up uptune-draft-<draft-id> in Webflow before retrying. Store the item ID and mark the record ready if the draft exists.
Related automations
Use the Product Listing Copy System for related product content and the Voice-to-Webflow FAQ Draft System for customer-facing changes. The Voice-to-Webflow SEO Review System reviews page metadata. Read the Content Publishing & Newsletter Intelligence blueprint for the wider content process.