Keep a WS Form consent log in monday.com

What the test form sent

A consent log needs to show what someone chose and when, in words anyone can audit later. This guide sends a WS Form preferences form to a board that does that.

We sent this through the live form on WS Form LITE 1.12.19, with connector 1.3.0. The table is what left WordPress. The last column is our suggestion.

The visitor chose Weekly digest, Product news and Event invites. None of those words reached monday.com.

Set readable values before you map

WS Form is the opposite of Ninja Forms, Forminator and MetForm, which all turn a stored value back into its label. The plugin has no such step for WS Form. Whatever is saved as the value is what your board gets, in Status labels, Dropdown labels and Full Response.

That’s a problem for a log. “Weekly digest” means something to an auditor, and weekly is close. A value such as opt_2 means nothing at all.

Each choice in WS Form sits in a data grid. Column Mapping decides which grid column is shown as the label and which is saved as the value. A new field has one column used for both, so its value is the label text. Our test form added a second column on purpose, so check this before you map:

1. Open the field’s settings and find Column Mapping.
2. If Labels and Values point to the same column, you’re done. The visitor’s wording is what arrives.
3. If they point to different columns, edit the value column so each entry reads the way it should on the board.
4. Submit a test entry and read the values on the board.

Do this first. The app creates a Status or Dropdown label from whatever arrives, so items you’ve already received keep the old wording.

Log every change as a new item

It’s tempting to keep one item per person and update it. For consent, don’t. Our second test submission left the radio and the checkboxes empty, and they arrived as empty text and an empty list. The app skips empty answers, so on an update they wouldn’t clear anything.

Picture someone who unticks every topic. An update would leave their old topics on the item, as if they’d never changed their mind. So use the create template, and let each submission be its own record:

Email preferences

Consent log

Name	Email frequency	Topics	Recorded
jo@example.com	weekly	news, events	2026-11-06 21:18
kai@example.com			2026-11-06 21:18

Sort the board by email, or filter on it, to see one person’s history. Then map Submission Date to a Date column. It’s the only timestamp you get, because Date/Time is a PRO field in WS Form, and it holds the date and time in UTC.

Once your site is connected, pick the form in Form ID, a group in Group/Item, then open Data:

The form has no name field, so Email fills both the item name and the Email column.

Rebuilding a form breaks the mapping

WS Form gives each field a database id, and everything downstream keys on it. We saw this directly: the same form had field ids 6, 7 and 8 in one test run and 2, 3 and 4 after it was rebuilt.

The app stores answers by field id, not by label, and it finds automations by form id:

The last two fail quietly, which matters for a consent log. If you rebuild a form, submit a test entry straight away and check the board.

Limits on LITE and the other routes

WS Form LITE doesn’t include Date/Time, Range or Rating, and Hidden is PRO too. The connector also supports select, number, phone and URL fields. See Supported WordPress form plugins.

Zapier’s template also creates a new item for each WS Form submission. Zapier alternatives compares the routes, and the WordPress forms to monday.com guide covers everything else.