Change a registration, withdraw one, read them back
The workshop from tutorial 02 is running. Somebody wants to move from the morning to the afternoon session, somebody else cannot come at all, and the organiser wants the roster on the event page. All three are the same idea: a record you can find again.
- The scenario
- The registration Sheet from tutorial 02 already has rows in it. Now those rows need to change without anybody editing the spreadsheet by hand.
- What you end up with
- A form that changes rows, a form that removes them, edit links on every row, and a read key your own page can use to show the roster.
- You need
- The existing registration form and its Sheet
- A Pro workspace — Update, Delete and Record Fetch are all Pro
- Somewhere to send each attendee their own link, or record reference
-
Your managed Sheet, column A
Meet webtzm_id, the handle everything else uses
Every row Webtzm writes starts with
webtzm_idin column A. It is how an Update finds the right row again, and how a Delete finds the right row to remove. Nothing else identifies a record — not the email address, not the name.Keep it in column AYou may reorder every other column. Move
webtzm_idout of the first column and Update and Delete stop being able to find rows. Move it back and they work again.The attendee does not have to type it. With edit links on, each row carries its own link to a Webtzm page where that one entry opens already filled in, and the submitter receipt includes it. The record ID stays the thread underneath, and it is still what your own code sends when it talks to Webtzm directly.
-
Setup › What it can do
Turn on Change rows
Open the registration connection's Setup. Under What it can do, turn on Change rows. Webtzm gives the connection a form named after it with
changes, which finds a row by its record ID or from an edit link, starts with the connection's own fields — every one optional, since any of them may change — and turns edit links on for every row, writing them into the rows already in the Sheet. There are no spreadsheets to fetch and no columns to look up: the connection is the pick.
Open full size
Each switch adds its form to the connection, listed under Forms in this connection. If the last step does not finish, What it can do offers Finish setup. For a page of your own that posts a change, the generated code — Get the form code beside the changes form — adds one field your fields did not: a required Record ID input, emitted visibly so the published form works as generated. The edit-link page below needs none. An update changes only the answers it receives filled in, so a question you leave off your page cannot be altered from it, which is the simplest access control there is.
Generated Update form HTML — for a changes form with two questions; note the webtzm_id field at the top <form class="wtzm-form" action="https://webtzm.com/submit" method="post" data-webtzm-form="YOUR_FORM_ID" data-wtzm-enhancement="client" data-wtzm-format-events="submit" data-wtzm-validation-style="red" data-wtzm-block-invalid="true" data-wtzm-validation-messages="true" data-wtzm-status-feedback="true" data-wtzm-lock-submit="true" data-wtzm-text-trim="true" data-wtzm-text-clean="true" data-wtzm-text-truncate="false" data-wtzm-text-max-chars="50000" data-wtzm-capture-referrer="false" data-wtzm-capture-utm="false" data-wtzm-capture-locale="false" data-wtzm-timestamp-zone="UTC"> <input type="hidden" name="_webtzm_form" value="YOUR_FORM_ID"> <div data-wtzm-field="webtzm_id"> <label for="webtzm_id">Record ID <span class="wtzm-required" aria-hidden="true">*</span></label> <input id="webtzm_id" type="text" name="webtzm_id" placeholder="The webtzm_id of the row to update" required> </div> <div data-wtzm-field="session"> <label for="session">Session</label> <select id="session" name="session"> <option value="">Select Session</option> <option value="Morning · 9am to 12pm">Morning · 9am to 12pm</option> <option value="Afternoon · 1pm to 4pm">Afternoon · 1pm to 4pm</option> <option value="Full day">Full day</option> </select> </div> <div data-wtzm-field="dietary_notes"> <label for="dietary_notes">Dietary notes</label> <textarea id="dietary_notes" name="dietary_notes" rows="4" placeholder="Enter dietary notes"></textarea> </div> <p data-wtzm-send-status role="status" aria-live="polite"></p> <button class="wtzm-submit" type="submit">Submit form</button> </form>Prefill it and hide itIf your page already knows which record it is editing — because the link carried the reference — change that input to
type="hidden"and prefill it. The attendee then sees only the questions they can answer. -
Setup › Advanced › Edit and remove links
Or skip the ID with edit links
An attendee should not have to find a record ID. Turning on Change rows already switched Edit links on: Webtzm writes a link into a column of the registration Sheet for every row, as each row arrives, and into the rows that were already there; Add links to existing rows does that again whenever you need it. Their settings are in Advanced, under Edit and remove links.
Open full size
The links sit in a Sheet column, so you can copy one for anyone. Show current answers opens the page with the entry already filled in. - The link opens a Webtzm-hosted page showing the connection's fields, filled in with that row's current answers when Show current answers is on. Submitting changes only the fields filled in, exactly like any update.
- Only accept changes from edit links refuses a change that arrives with just a record ID, including from your own code. Leave it off while existing code still sends IDs.
- Reset all links makes every link handed out so far stop working, and gives each row a new one. Do it if a link was shared more widely than meant.
- Remove rows gives each row a Remove link instead. Its link opens a page that asks before anything is removed.
A link is the key to one rowAnyone holding an edit link can change that one entry, which is the point of it. Treat it like the entry itself: send it to the person it belongs to, and reset the links if it travels further.
-
Know exactly what an update touches
An update changes only the answers it receives filled in. A field the visitor leaves blank keeps whatever the row already holds, so somebody who answers one question does not empty the rest.
The attendee submits The stored row session= Afternoon,dietary_notesblanksessionchanges; the existing dietary note is keptBoth fields filled in Both change Both left blank Nothing changes Your own code sends nullfordietary_notesThe cell is emptied, and stays empty A blank box cannot clear an answerA blank and a question the update never asked look identical, so a blank is treated as “no change”. To empty a stored answer on purpose your own code sends
nullfor that field. A published form cannot send it, so only your own code can clear a stored answer. -
Setup › What it can do
Turn on Remove rows
Remove rows works the same way: turning it on gives the connection a form named after it with
removals, which deletes the managed Sheet row. It needs only the record reference, so it has no fields at all, and its generated markup supplies the one input it requires.Generated Delete form HTML — the same shape, one word different <form class="wtzm-form" action="https://webtzm.com/submit" method="post" data-webtzm-form="YOUR_FORM_ID" data-wtzm-enhancement="client" data-wtzm-format-events="submit" data-wtzm-validation-style="red" data-wtzm-block-invalid="true" data-wtzm-validation-messages="true" data-wtzm-status-feedback="true" data-wtzm-lock-submit="true" data-wtzm-text-trim="true" data-wtzm-text-clean="true" data-wtzm-text-truncate="false" data-wtzm-text-max-chars="50000" data-wtzm-capture-referrer="false" data-wtzm-capture-utm="false" data-wtzm-capture-locale="false" data-wtzm-timestamp-zone="UTC"> <input type="hidden" name="_webtzm_form" value="YOUR_FORM_ID"> <div data-wtzm-field="webtzm_id"> <label for="webtzm_id">Record ID <span class="wtzm-required" aria-hidden="true">*</span></label> <input id="webtzm_id" type="text" name="webtzm_id" placeholder="The webtzm_id of the row to delete" required> </div> <p data-wtzm-send-status role="status" aria-live="polite"></p> <button class="wtzm-submit" type="submit">Submit form</button> </form>Put a confirmation in front of itA form that posts a record ID removes a row the moment it is submitted. Ask “are you sure?” on your own page first — Webtzm will not ask on your behalf, and the row is gone from the Sheet afterwards. Remove links are the exception: their Webtzm page asks before removing anything.
-
Setup › Google output
Or hand each record to another system as JSON
There is a second way out of Webtzm that involves no spreadsheet at all. Turning on JSON as a connection's Google output writes one versioned UTF-8 record per submission into a Drive folder — a handoff for an automation, an import, or an archive that has to outlive the tool that made it.
One delivered JSON record — read back out of Drive, unedited { "schema_version": "webtzm.submission.v1", "submission": { "id": "3a0c3d0a-e9ac-4b3b-a963-52333ed0d79e", "accepted_at": "2026-09-07T09:50:53.268Z", "synced_at": "2026-09-07T09:51:30.548Z", "timezone": "UTC", "timestamp_format": "iso", "fields": { "name": "Daniel Okafor", "email": "daniel.okafor@example.com", "session": "Afternoon · 1pm to 4pm" } } }The version is part of the contractschema_versionnames the shape of the record. Your reader should check it rather than assuming, so that a future shape is something your code can notice instead of something it silently mis-reads. Your own answers stay together underfields; everything Webtzm adds sits outside it.This is the opposite trade from a Sheet: nothing is readable at a glance, and everything is readable by a program.
-
Setup › Advanced › Read records
Let your own page read the roster back
Adding, changing and removing rows all describe what a submission does to a Sheet. Fetch is the other direction: your application asks Webtzm for the rows a connection created, and gets them back as JSON. Turn on Read records under What it can do, then set it up in Advanced, under Read records: keys and columns.
Open full size
Nothing is readable until you pick it. Turn on shares every column; Choose columns lets you pick first, and removing a column takes effect immediately. - Keep Record id readable when your page will later offer an update or a withdrawal — that is the handle those need.
- Do not share a column just because it exists. An attendee's dietary note has no business on a public roster.
- Under Developer options, Live, Standard and Economy decide how current the answer has to be: every request, one minute, or five. Standard is right for almost everything.
Reading the records from your own server — the key goes in a header, never in a URL curl -H "Authorization: Bearer YOUR_SERVER_KEY" \ "https://webtzm.com/fetch/YOUR_FORM_ID?limit=50"A browser key is publicAnyone who loads the page can read a browser key, so every column you shared becomes public. The console asks you to acknowledge that before it will create one, under Developer options. A server key belongs only on a server you control, and is shown once and never again.
Fetch never writes. Rows change only through a submission, and the Sheet is always the source — a row somebody edited by hand appears in every freshness setting.
The loop, closed
The four things a form can do fit together as one cycle, and webtzm_id is the thread through all of them.
| What the form does | Direction | Needs the record reference |
|---|---|---|
| Add rows | Form → new Sheet row | No — it produces one |
| Read records | Sheet rows → your application | No — it returns them |
| Change rows | Form → existing row | Yes, or an edit link |
| Remove rows | Form → row removed | Yes, or a remove link |
Fetch reads only Sheets that Webtzm created for the form. A spreadsheet you supplied by hand cannot be read back, and the panel says so rather than offering a control that would fail later.