How it works
What this workflow does
Read a Webflow CMS item, turn a spoken edit brief into an SEO title and description, and log the proposal next to the existing metadata for an editor. The workflow never writes to Webflow; it gives the team a reviewed suggestion and the CMS snapshot needed to apply it safely.
The workflow imports inactive with dryRun: true. Run with sample data uses a fictional CMS item and metadata, so the preview does not call Webflow, OpenAI, or Google Sheets.
This is the metadata-review layer for the Content Publishing, Social Distribution & Newsletter Intelligence blueprint; the Campaign Launch Assurance & Weekly Performance blueprint covers search and campaign performance.
The private form
Receive event is an n8n Form Trigger protected by Basic Auth. Editors get fields for Draft ID, Webflow CMS item ID, Target search query, the dictated Edit angle, and Verified facts about the page. The draft ID must be stable and lowercase; the item ID must be a 24-character Webflow identifier.
A live run also requires the Webflow collection ID, a spreadsheet ID, the OpenAI model, and the CMS field slugs mapped to the current SEO title and description.
Snapshot, propose, review
The workflow checks the Webflow SEO Review sheet for the request ID, then reads the CMS item with the Webflow API. It requires the requested active item, captures the page name and slug, reads the current title and description from the configured field slugs, and records the item's last-updated timestamp.
OpenAI returns a title of at most 60 characters, a description of at most 155 characters, a short rationale, and one exact evidence quote from the approved facts. The workflow rejects links, HTML, line breaks, unsupported evidence, and numbers that do not appear in the page name or approved facts.
The review row preserves the current metadata, suggested metadata, rationale, evidence, target query, and CMS snapshot. The editor compares the snapshot and the live page before applying changes in Webflow. A repeated request ID stops before a second review row.
Validation scope
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 current-and-proposed metadata retention, archived-item rejection, invalid SEO copy, duplicate requests, and read-only Webflow behavior. Live Wispr Flow dictation, deployed forms, credentials, model responses, Webflow reads, and Google Sheets writes require staging.
How to use
Before you start
- A current n8n instance with Form Trigger support.
- A Webflow account, site, and CMS collection with SEO metadata fields.
- A Webflow API token with
cms:read. - An OpenAI API key and a JSON-mode model.
- A Google spreadsheet tab for the SEO review queue.
- A Google Sheets OAuth credential.
- Wispr Flow configured for the editors who will dictate.
1. Import and run the sample
Download the complete package, extract the ZIP, and read the full setup guide. Import voice-to-webflow-seo-review.n8n.json and keep it inactive.
Open Run with sample data and choose Test workflow. Assemble SEO review proposal should return current and suggested metadata with evidence.
2. Prepare the private form
Select a Basic Auth credential on Receive event. Start the form test and open the Test URL. Dictate the edit angle with Wispr Flow, review the inserted text, and submit.
3. Configure Webflow and the sheet
In Setup, enter the collection ID, spreadsheet ID, model, and editorial voice. Set currentTitleField and currentDescriptionField to the API slugs of the collection fields mapped to your SEO metadata. Clear either field when it does not exist.
Select a Webflow Header Auth credential on Read Webflow CMS item with cms:read. The workflow reads the record, including its last-updated timestamp. In a localized site, the default API lookup targets the primary locale.
Create the tab Webflow SEO Review with these exact headers:
| Request ID | CMS Item ID | Page | Slug | CMS Snapshot | Target Query | Current SEO Title | Current Meta Description | Suggested SEO Title | Suggested Meta Description | Rationale | Evidence | Status |
|---|
Connect Google Sheets OAuth on both Sheets nodes.
4. Connect OpenAI and test
Add an OpenAI Header Auth credential on Draft SEO metadata. Enter a Webflow CMS item ID and target search query, then dictate the edit angle and add verified page facts. Use the supplied test payloads to check the item, current metadata, and model output.
The sample includes current and suggested metadata. Suggested titles and descriptions are capped at 60 and 155 characters as editorial defaults. A different or archived CMS item, invented claim evidence, or a repeated request ID stops before a new review row.
5. Review and apply
Check the suggested wording against the actual page and search intent. Compare the recorded CMS timestamp before applying changes in Webflow. The review row is the editorial proposal; the workflow itself does not modify the page.
Related automations
Use the Search Content Decay Detection System to find pages that need attention, and the Voice-to-Webflow Article Draft System to create new content. The Source-Backed WordPress Draft System covers non-Webflow publishing. Read the Content Publishing & Newsletter Intelligence blueprint for the wider content process.