Skip to Content
BlogWhat Validation Can You Set on a monday.com Form?

What Validation Can You Set on a monday.com Form?

Published on October 6, 2026

A public form with no validation collects whatever people type. Phone fields fill up with “N/A,” email fields fill up with typos that bounce every automation downstream, and a numbers field takes “twenty” as an answer. Before you build the form, it helps to know exactly what each tool will actually stop before it reaches your board.

monday.com’s native WorkForms and FormFlow do not validate the same amount. Here is what each one checks, sourced to their own documentation, and one bug worth knowing about before you rely on required fields inside conditional logic.

Quick answer

  • WorkForms’ entire validation surface is a Required toggle plus a non-configurable Email format check — no length limits, no custom messages, no pattern rules.
  • FormFlow’s form builder adds format validation (email, phone, URL), length limits and custom rules, and custom error messages per field.
  • A documented WorkForms bug: required validation still fires on fields hidden by conditional logic, blocking submission on a question the respondent never sees.
  • Install FormFlow and set format and length rules on the fields that need them.

What WorkForms Validates

Per TaskRhino’s review of WorkForms field validation , WorkForms ships two validation behaviors, and that is the complete list as of early 2026:

  • Required — mark a field as required; the form will not submit if it’s left blank.
  • Email format check — an Email-type question checks for a basic something@something.something pattern. The rule isn’t configurable, and it doesn’t catch malformed addresses like a domain-less “name@” that still passes and later bounces on downstream email automations.

There is no length limit, no numeric range, no phone or URL format check, and no way to write a custom rule or error message anywhere in WorkForms’ validation options.

The Hidden-Field Validation Bug

The same TaskRhino review documents a specific failure mode: when a required field’s question is hidden by conditional logic, the required check still fires. The respondent can’t submit the form, even though they never saw the field that’s blocking them. The only native workaround is to leave the field optional and accept that “required” then means nothing once conditional logic is involved — WorkForms has no way to make a field required only while it is visible.

If your conditional logic hides fields based on earlier answers, check every required field behind a condition against this bug before you publish the form.

What FormFlow Validates

FormFlow’s form builder documents four validation settings per field, configured alongside the field’s label and default value:

  • Required validation — same required/optional toggle as WorkForms.
  • Format validation — email, phone, and URL fields check against their expected format.
  • Length limits and custom rules — set minimum and maximum length, plus additional rules beyond a plain required toggle.
  • Custom error messages — write the message a respondent sees when a field fails validation, instead of a generic error.

The field library maps each of these onto specific monday.com column types — Text, Email, Phone, and Link columns are the ones where format validation applies directly, since those are the input types the format check targets.

FormFlow’s documentation does not break “custom rules” down into a list of specific pattern types (regex, numeric ranges, and so on), so confirm the exact rule options available for your field type in the builder before depending on a specific validation pattern for launch.

Validation Side by Side

Validation typeWorkFormsFormFlow
Required fieldYesYes
Email format checkYes (fixed, not configurable)Yes
Phone format checkNoYes
URL format checkNoYes
Length limitsNoYes
Custom validation rulesNoYes (exact rule types: confirm in builder)
Custom error messagesNoYes
Required respects hidden fieldsNo (documented bug)Not documented — test before relying on it

Where This Matters in Practice

Lead and contact forms. A Phone or Link field with no format check collects whatever a respondent types, including plain text. If a sales team routes leads by phone number into an autodialer, an unformatted or missing area code breaks the automation quietly.

Long-form intake. A Long Text field with no length limit can arrive at 10,000 characters that don’t fit a board’s item view cleanly, or a two-word answer to a question that needed detail. A minimum and maximum length catches both directions.

Forms behind conditional logic. Any form using visibility rules to show or hide fields based on earlier answers should treat every required field behind a condition as a place to double check — WorkForms’ behavior here is a documented bug, and FormFlow’s docs don’t state either way whether a hidden required field blocks submission, so verify it directly in your own form before launch.

Frequently Asked Questions

Does monday.com WorkForms support regex or pattern-based validation?

No. Per TaskRhino’s review of WorkForms validation, the only built-in checks are a Required toggle and a fixed Email format check — there’s no way to write a custom pattern rule.

Can I set a minimum or maximum length on a WorkForms text field?

Not natively. WorkForms has no length-limit setting for any field type; a Long Text answer can be one character or several thousand with no validation stopping either.

Does FormFlow support phone number formatting validation?

Yes. FormFlow’s form builder documents format validation for phone fields alongside email and URL fields, checked against the expected format for that field type.

Will a required field hidden by conditional logic block submission?

In WorkForms, yes — this is a documented bug where a required field still blocks the form even when its question is hidden. FormFlow’s documentation does not specify this behavior either way, so test it directly in your own form before relying on it for a form with visibility rules.

Next Steps

Last reviewed: 2026-10-06. WorkForms validation behavior and the hidden-field validation bug verified against TaskRhino’s review of monday.com form field validation . Features and limits may change.

Last updated on