Turn each questionnaire response into a Google Doc
A clinic sends a short questionnaire after every visit. The practice manager reads them one at a time and files them, so a spreadsheet row is the wrong shape — each response wants to be a document.
- The scenario
- A post-visit questionnaire that already exists on the clinic's site, written by whoever built the page. Nobody wants to rebuild it; they want it delivered somewhere useful.
- What you end up with
- One Google Doc per response, created from your own styled template, in a Drive folder you control.
- You need
- Sheets and Drive connected
- A Pro workspace — Google Doc is a Pro output
- The questionnaire's existing HTML, and the domain it is published on
-
Setup › Questions › Paste your form
Paste the markup you already have
Make the connection with New connection and name it
Visit feedback. In its Setup's Questions, select Paste your form: it takes your form's code and reads its fields, their types and which are required. Webtzm does not scan a page URL and does not guess which form on the page you mean — you paste the one form you want connected.
Open full size
The editor formats itself after a paste, so pasted markup from a page builder becomes readable before you check it. The questionnaire as it exists on the clinic's site — paste this, then select Use these fields <form id="visit-feedback"> <label for="patient">Your name</label> <input id="patient" name="patient" type="text" required> <label for="visit_date">Date of visit</label> <input id="visit_date" name="visit_date" type="date" required> <label for="rating">How was your visit?</label> <select id="rating" name="rating" required> <option value="Excellent">Excellent</option> <option value="Good">Good</option> <option value="Fair">Fair</option> <option value="Poor">Poor</option> </select> <label for="comments">What could we do better?</label> <textarea id="comments" name="comments" rows="4"></textarea> <button type="submit">Send feedback</button> </form> -
Setup › Questions
Check what was mapped, and what was skipped
Use these fields replaces the connection's questions with the ones it read, and says how many it used. When it has to leave a control out it says how many and asks you to give each one a name; the ones it leaves out matter more than the ones it used.
Open full size
Four fields, none left out: the line under Use these fields says how many were used, each chip shows a question's label and kind, and the heading counts how many are required. What could we do better? is the one that is not. To check what each one became in the Sheet, select Edit questions. The settings beside the list show the selected question's Parameter, which is its column header: How was your visit? is stored as
rating.A skipped control is a silent gapThe usual cause is a control with no
name. It renders, the visitor fills it in, and it is never submitted by the browser. If any control was left out, fix the markup before going further — a column that never arrives is much harder to notice later. -
Setup › Google output
Turn on the Doc output
Open full size
Doc copies and populates your template once per submission. PDF does the same and then exports — see the job application tutorial. The Drive folder is named before anything is created, so you find out where the documents will land while you can still change it. Turning the Doc output on gives the connection a starter template in its Drive folder, with a variable for every field:
{{patient}},{{visit_date}},{{rating}},{{comments}}. Open the Doc template, under the outputs, opens it.Write the template in Google Docs the way you want the finished response to read — the clinic's letterhead, the question wording, a space for the manager's note — and put a variable everywhere an answer belongs. Webtzm copies the template per submission and fills the variables in; it never edits your original.
-
Setup › Advanced › Security
Decide how long Webtzm keeps its own copy
Health-adjacent answers deserve a deliberate answer to this question rather than a default.
Open full size
Free redacts submitted values once delivery finishes. Pro can keep them for 7, 30 or 90 days. - Retention governs Webtzm's copy of the submitted values. Delivery status and audit metadata are kept either way.
- It removes nothing from Google. The Docs in your Drive are yours and stay until you delete them.
- A shorter window means less to resend if a delivery later needs another attempt. That is the trade.
-
Your own site
Replace the published form with the generated one
Pasting your markup gave Webtzm the field map. It did not connect your published page. Copy the generated code from Get the form code, in the connection's Advanced, and replace the form on the site with it — that version carries the form id, the anti-spam check and the status region.
Then submit one invented response and confirm Delivered in Analytics.
What lands in Drive
Open full size
One Google Doc per response, named after the form and the submission, inside the folder named under the output — by default Webtzm / [form name] in the Drive of the account you connected.
- The Doc is a normal Google Doc. Comment on it, share it, move it, edit it — Webtzm does not read it back.
- Your template is untouched. Each submission copies it.
- Nothing links the Doc back into Webtzm, so if you also want the answers in a table, add a second form with a Sheet output on the same page.
If somebody asks “what proportion said Fair or Poor last quarter”, a folder of documents cannot answer it. Choose the Doc output when each response is read individually, and add a second form with a Sheet output when they will also be aggregated.