How it works
What this workflow does
Turn the wording your support or sales team actually uses into a Webflow FAQ draft. The editor opens a private n8n form, dictates the answer, reviews it, and supplies the current approved policy. The workflow validates the input, drafts a short answer with supporting details, and creates a staged Webflow CMS item that keeps the customer question as the item name.
The workflow imports inactive with dryRun: true. Run with sample data uses a fictional kickoff question and policy, so the preview does not call OpenAI, Webflow, or the Data Table.
This is the FAQ layer for the Content Publishing, Social Distribution & Newsletter Intelligence blueprint; the Support Escalation & Ticket Intelligence blueprint covers the support operations behind the approved guidance.
The private form
Receive event is an n8n Form Trigger protected by Basic Auth. Editors get fields for Draft ID, Customer question, Dictated answer, and Verified answer or policy. The customer question must be one line. The draft ID must be a stable lowercase value. A live run also requires a Data Table, model, 24-character Webflow collection ID, and valid distinct CMS field slugs.
The default Rich Text field slug is answer and the default Plain Text field is short-answer.
Evidence and numeric checks
OpenAI returns a short answer, supporting details, and one evidence quote. The quote must appear exactly in the verified policy and must be between 12 and 260 characters. The short answer and details are length-checked and must be plain text.
Any number in the answer or details must also appear in the verified policy. The workflow escapes the content and builds the CMS body from the short answer and details. It keeps the supplied question as the CMS item name and verifies 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 preservation of the supplied question, verified-policy evidence, escaped Rich Text HTML, 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 FAQ 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.
- Current approved support or sales guidance.
1. Import and run the sample
Download the complete package, extract the ZIP, and read the full setup guide. Import voice-to-webflow-faq.n8n.json and keep it inactive.
Open Run with sample data and choose Test workflow. Assemble FAQ draft should return the short answer, explanation, and evidence.
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 answer 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, such as answer, and summaryField to the Plain Text field slug, such as short-answer. Clear the summary field if the collection does not use one. Configure any other required fields before staging.
Select a Webflow Header Auth credential on Create Webflow CMS draft with cms:write. Add an OpenAI Header Auth credential on Draft with OpenAI. The workflow uses the staged-item endpoint; review and publish in Webflow.
4. Test and operate
Enter one customer question and dictate a short answer. Add the current approved guidance in the verified field. The workflow keeps the question, includes the short answer and explanation, and rejects any quote missing from the verified guidance.
Check scope, eligibility, timing, and policy wording in the staged draft before publishing. Use a new draft ID to propose another revision.
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 Source-Based Checklist System for a related support handout and the Voice-to-Webflow Article Draft System for long-form guidance. The Voice-to-Webflow SEO Review System reviews the page metadata after publication. Read the Content Publishing & Newsletter Intelligence blueprint for the wider content process.