Keep the form you already built. Webtzm routes every submission straight into Google Sheets, Docs, or Drive — including file uploads Pro plan — with no backend to build, deploy, or host.
Google Sheet
your selected output 200 OK
Google Doc
PDF or JSON
Drive upload
You keep the form. Webtzm carries each accepted submission. The record lands in the Google file you chose, and your team takes it from there.
Generate form HTML in Webtzm, or connect the form already on your page.
One selected Google output per workflow, so every submission lands somewhere you already trust.
Delivery is visible, not assumed.
The record is a normal Google file, not an export you have to request.
This interactive preview shows one submission per Sheet row, with each answer in a clear column and a simple delivery status.
<form action="YOUR_WEBTZM_SUBMIT_URL" method="POST"
data-webtzm-form="YOUR_WORKFLOW_ID">
<input name="name" placeholder="Maya Lee" required>
<input name="email" type="email" placeholder="maya@example.com" required>
<textarea name="message" placeholder="Please add me to the Saturday workshop list."></textarea>
<p data-wtzm-send-status></p>
<button>Send test message</button>
</form>
<script src="YOUR_WEBTZM_ENHANCE_URL"></script>The three YOUR_... placeholders are filled in for you when you create a form — the console hands you this same snippet with your real endpoint, workflow ID, and script URL. This demo does not contact Google; the Form tab simulates the protected submission check and adds a preview row for the workflow.
| reference | name | message | |
|---|---|---|---|
| 1 | Amira Noor | amira@example.com | RSVP for Saturday class |
| 2 | Daniel Park | daniel@example.com | Workshop timing question |
Collect the submission, send it to one selected Google output, then review, share, and act on the record.
Protect, accept, and relay with Webtzm
RSVPs, lesson check-ins, guardian notes, and workshop records become clean attendance history.
One attendance row with each submitted field in its own column
Use the same intake-to-Google path for:
…and whatever needs a clean path from a public form into your workflow.
Connect forms from page builders, CMS platforms, static hosts, or plain HTML, then keep the submitted data in Google.
For pages drafted with tools such as Claude, ChatGPT, Gemini, AI Studio, or v0. A preview inside the tool runs at the tool’s own address, so that address is the allowed domain while you test, and your own host is once you publish.
For hosted pages where Framer, Webflow, WordPress, or Wix owns the presentation, and Google should own the submitted data.
For public pages that can show a form but still need a dependable way to accept submissions and deliver them to Google.
For anyone adding the Webtzm setup code to a form they already own.
Connect Webtzm to Claude, ChatGPT, Cursor, or another assistant with one URL. It can put a form on the site it is building, create new forms, and check that submissions are arriving.
Add a contact form to this site and send the replies to a Google Sheet.
Done. I created a Contact form in Webtzm that delivers to a new Google Sheet, added it to contact.html in your site’s own styling, and allowed your site’s domain to send submissions.
Have today’s submissions arrived?
Yes. Three arrived and none need review.
Connector URL: https://webtzm.com/mcp/workspace
Google Forms is the quickest way to get a form online when its built-in design fits. Webtzm is for the page you already built. Both end in the same place—your Sheets, your Docs, your Drive—so the only real question is whose form your visitor sees.
Use Google’s form editor, hosted form design, and response flow when that standard experience meets the need.
When the form is part of your product or brand, and still has to land in Google.
Either route lands in the same place: your Sheets, your Docs, your Drive, with no backend in between.
| What you are deciding | With Google’s form | With your own form |
|---|---|---|
| The page your visitor sees | Google’s editor and hosted layout | Your own page, markup, and styling |
| Where a submission lands | A linked Google Sheet | One output you pick: Sheet, Doc, PDF, JSON, or full-record email |
| If you need file uploads | Respondents sign in to a Google account | No respondent sign-in; Pro uploads save to your Drive |
| Getting the data back out | Export a file, or read the Sheet by hand | Your own app fetches the rows as JSON, with the columns you choose |
| Before it reaches your records | Google’s built-in response validation | Spam, limits, and repeat-submission checks, plus delivery status you can see |
Every plan states its limits plainly — pick the capacity, outputs, and upload room your forms need today, and grow into more the moment they need it.
For a first public form, or a small workflow that sends responses straight to a sheet.
No card, no expiry.
Best for text-only responses.
For busy forms that need file uploads, more delivery choices, and room to grow.
Standard price $5/month
Standard price $49/year
Less than a coffee a month. Free for 7 days if you haven't tried Pro.
For high-volume forms that need more room for workflows, responses, and uploads.
Standard price $49/month
Monthly only. No yearly price or trial.
What to know about accounts, limits, delivery timing, and the handoff from public forms into your Google workspace.
Google Forms is good when you want its built-in editor, hosted design, and response experience. Webtzm fits when you want to keep your own form or page—including Pro file fields—and send each accepted submission to one selected Google output.
Webtzm adds spam protection and sends accepted submissions to Google without asking you to maintain a public database or custom form service.
No. A normal gmail.com account can connect. Free uses a managed Google Sheet. Pro can instead create a Google Doc, PDF, JSON file, or full-record email. Email output and metadata-only notifications require separate Gmail permission and remain subject to Google's sending limits.
Webtzm accepts valid submissions before delivering them to Google. A busy period does not make the public form wait for Google to finish, and the dashboard shows what is still in delivery. Google account and service limits still apply.
Temporary delivery failures retry a limited number of times with backoff. If delivery still cannot complete, the record moves to a needs-review state so the owner can see that attention is required; Webtzm does not promise to wait indefinitely for a quota reset.
Yes. After delivery, you control the Google record and decide which people, automations, or external tools may access it through your Google sharing settings.
Yes, on Pro. Add one or more file fields and Webtzm sends approved documents or images straight to your Google Drive. A submission can include up to 3 files, with a limit of 25 MB per file and 75 MB in total. You can keep the recommended settings or narrow the allowed types and sizes for your form.
Yes, on Pro. Choose one primary output per workflow: a Sheet row, Google Doc, PDF, JSON file, or full-record email. A short owner alert from Webtzm is included on every plan. Pro sends that owner alert from your own Gmail instead and adds submitter receipts and failure alerts, each a separate metadata-only notification.
Yes. Every workflow gets an owner-only test page that sends a real first submission before any domain is published, and you can set a success redirect so a plain form post lands on your own page instead of a Webtzm one. Pro can also add an outbound webhook: a signed copy of each accepted submission posted to a URL you set.
Only the domains you list. Every form requires at least one allowed domain before it can go live — that is what stops someone copying your endpoint onto a page of their own. A submission from anywhere else is refused: no submitted value is stored, only the refusing site's address, kept in a short list so the form's owner can allow it with one click. List the exact domain you publish on, without https:// and without a path. A form that works locally and is refused once published is almost always a domain that has not been added yet. The user guide covers it in full.
Webtzm requests the narrow drive.file scope. It works with files it creates for you and files you explicitly select or share with it, rather than receiving broad access to everything in Drive.
Yes. In an Advanced workflow, choose an existing spreadsheet through Google's own file picker instead of letting Webtzm create one for you — the file stays yours. Webtzm keeps only the same narrow drive.file access described above; Update, Delete, and Fetch remain available only on a Sheet Webtzm created.
Free keeps submitted values only until delivery succeeds or reaches a terminal failure, then redacts them. Pro lets you choose 7, 30, or 90 days. Webtzm keeps non-sensitive delivery status and audit evidence after values are redacted, while your selected Google output remains under your Google account's controls.
Webtzm keeps submitted values long enough to deliver the selected output and troubleshoot an active failure. Free redacts values at terminal delivery; Pro follows the workflow's 7, 30, or 90-day retention setting. The selected Google output remains the durable working record you control.
Yes. Use it for personal records, clubs, classes, household planning, community projects, professional intake, or any public form that should become organized Google data.
Yes. Webtzm checks required fields, formats, spam, monthly allowance, repeat submissions, and the page allowed to send the form. Text has a 256 KB submission limit. Pro uploads can be limited by file type, file count, and size, up to Webtzm’s 3-file and 75 MB total cap.
Free includes 3 active form connections and 100 accepted submissions per month. Pro includes 50 active form connections and 10,000 accepts. Monthly-only Pro Scale includes 500 active form connections and 100,000 accepts. Webtzm manages delivery safely, while each connected Google account’s own service limits still apply.
Yes. Create the workflow, copy the setup code from the dashboard, and paste it into your page. It includes the form connection, spam protection, field support, and file uploads when the workflow uses files.
Yes. Webtzm has a connector for AI assistants that support MCP, including Claude, ChatGPT, Cursor, VS Code, and Gemini CLI. Paste one URL into the assistant, sign in with Google, and choose a workspace.
The assistant can then list your forms, put the form code into the site it is building, create a form, change its settings, and pause or resume it. You choose View only or View and make changes. It never reads what visitors submit, and it cannot delete a form, change billing, or connect or disconnect Google. The user guide has setup steps for each assistant.
No. Webtzm provides the public form connection and Google setup. You add the provided setup code to your page instead of building a custom form service or database.
Yes, on Pro and Pro Scale. Rows Webtzm created carry a record ID, so an Update or Delete workflow can change the right row without replacing the whole Sheet. Free shows both choices with a Pro label but keeps them disabled.
Yes. Workspace controls include export, suspension, and deletion. Review the dashboard guidance before deletion so you understand what remains in Google and what Webtzm data is removed.
