What a monday.com Form Can Check: Email, Phone, Dates and Regex by Plan
We’re a certified monday.com partner: we set up monday.com forms and build custom forms and apps, our own forms app BoardBridge among them. We don’t sell Fillout, Jotform or any other form app named here. Here’s how we reviewed this guide.
On Standard, a monday.com form only checks that required questions are answered. On Pro and Enterprise, board data validation rules also check numbers and dates. No plan has a rule for email or phone formats or custom patterns (regex).
Make the questions that matter required, offer choices instead of free text, and on Pro or Enterprise add number and date rules. For email, phone and code formats, review answers as they arrive or use a form app.
Quick answers
- On Standard, a form checks only that required questions are answered. Field by field
- Number and date rules come from the board’s data validations, on Pro and Enterprise. Set a rule
- No plan checks email, phone or code formats, so review answers or use a form app. Pattern checks
Native checks are enough when
- Answers come from a list you can offer as choices
- Numbers must be over a set amount, or dates from a set day
- Someone reviews new items before automations use them
Look past them when
- Codes or IDs must match a pattern
- An email or phone number typed wrong breaks an automation
- A date must be after today, whatever today is
What a form checks
- Standard Required questions
- Pro and Enterprise Number and date rules
- Email, phone, patterns No plan has a rule
From monday.com’s Help Center articles on data validations and WorkForms question types, as read Oct 27 to 29, 2026; the Help Center answered with a bot check on Nov 15, 2026. Checked on Nov 15, 2026.
What are you trying to do?
Pick one to jump to your part of the page.
See what my form checks today:
One table, field by field: what a form checks on Standard, what Pro and Enterprise add, what a form app adds, and the cheapest fix for each.
Add number and date rules:
On Pro and Enterprise, data validation rules on the board’s columns also check form answers. Where the rule lives, its three limits, and how to test it.
Bad emails and phone numbers get in:
No plan checks their format. Catch them as they arrive, on any plan: choices instead of free text, the format in the question, a review status before automations run.
I need regex or pattern checks:
Fillout and Jotform check patterns, lengths and formats before people can submit, and write to your board. What each checks, on which plan, from their own pages.
Set the checks up for us:
We set up required questions and data validation rules, a review step before your automations run, or a form app with pattern checks wired to your board, and build custom forms and apps: 25+ custom monday.com apps so far.

On Standard, a monday.com form only checks that required questions are answered. On Pro and Enterprise, board data validation rules also check numbers and dates. No plan has a rule for email or phone formats or custom patterns (regex). The rest of this guide is the field-by-field answer, how to set a number or date rule, how to catch bad answers on any plan, and which form apps check patterns before people submit.
What most people call input validation, a check that runs before a respondent can submit, comes in monday.com from two places: the form’s own “required” setting, and the board’s data validation rules on Pro and Enterprise. Everything else a form takes as typed. Building the form itself is in our guide to creating a monday.com form; every other form limit, plan by plan, is in monday.com WorkForms limitations.
What a Form Checks, Field by Field
Each form question fills one column of the board, so what a form can check depends on the question type and the plan. This table puts the fields people ask about side by side. The monday.com columns are from its Help Center articles as read Oct 27 to 29, 2026; the form app column is from Fillout’s and Jotform’s own pages as read Nov 15, 2026, not tested by us.
| Field | Standard | Pro and Enterprise (data validations) | Form app (Fillout, Jotform) | Cheapest fix |
|---|---|---|---|---|
| Required or not; fills an Email column; monday.com documents no format check | No email rule documented | Fillout can check the address really exists (a paid add-on); Jotform can make people confirm it before they submit | A confirmation email to the address given; a bounce flags it | |
| Phone | Required or not; fills a Phone column, with an optional default country prefix | No phone format rule | Jotform’s input mask fixes the format as people type; Fillout’s regex on a text field | Set the country prefix and show the format in the question |
| Number | Required or not; fills a Numbers column | A rule such as “over a set amount” | Fillout’s condition rule | A Number question, never a text one |
| Date | Required or not; an optional “Today” default | Only dates from a set date; no rule relative to today | Not on the pages we read | A rule from a set date, and a review for the rest |
| Short text, codes and IDs | Required or not; any text goes | No pattern or length rule documented | Fillout: min and max length, regex or condition, your own error message; Jotform: a validation option, a character limit and an input mask | Show the format in the question; review as answers arrive |
| Choices (single and multi select) | Only the listed choices; a multi select can cap how many are picked | Not needed for most | Not needed for most | Use choices wherever the answer comes from a list |
Two things stand out. First, the choice questions are the only native check that works on every answer, on every plan: a respondent can’t type a wrong country or service when they have to pick one. Second, the Phone question’s default country prefix is set once on the question, so people start from the right code instead of typing it; it does not check the rest of the number. The full list of question types, and which column each fills, is in creating a monday.com form; which form features each plan has is in monday.com form features by plan.
What a respondent sees when they type a badly formed email into the Email question, monday.com’s articles we read don’t say. Test it before you rely on it: submit “abc” and a misspelled domain to your own form and see what lands on the board.
Number and Date Rules on Pro and Enterprise
On Pro and Enterprise, monday.com’s data validations are rules on the board’s columns. They apply wherever the column is filled: on the board, by automations, through the API, and in WorkForms submissions, as long as the column is in the form (monday.com Help Center, as read Oct 27, 2026). monday.com’s own examples are a Numbers column that must be over a set amount and a Date column that only accepts dates from a set date.
Where the Rule Lives
The rule is set on the board, not in the form editor. Three steps, as monday.com’s article describes the feature:
- Put the column in the form. A rule checks form answers only when its column is one of the form’s questions.
- Set the rule on the board’s column. Open the data validations for that column on the board and set the limit, such as a number over a set amount or a date from a set date. monday.com’s article “Data validations” has the menu steps.
- Try it as a respondent. Open the form’s shared link, give an answer that breaks the rule, and see what the form says and whether anything reaches the board.
The third step matters because the articles we read don’t show the message a respondent sees when a rule stops them. Write what you find in the question’s description, so people know the limit before they hit it.
The Three Limits of These Rules
The column must be in the form
A rule on a column the form doesn’t ask about checks nothing in the form.
No dates relative to today
A Date rule can accept dates from a set date. Rules such as “the date is not yesterday” or “after today” aren’t supported, so a set date has to be moved by hand when it should move.
A conditional rule breaks if its second question is hidden
Data validations can link two columns (if one holds a value, the other must too), but in a form the rule doesn’t work when its “if” question appears and its “then” question is hidden by the form’s logic. Showing and hiding questions is in show and hide fields in monday.com forms.
Two related rules are worth knowing apart. A form’s own “required” setting works on every plan and stops a blank answer in that form. Required columns are a board rule on Pro and Enterprise: an item can’t be created or updated without those columns, and an automation that tries fails with a message in its History; how they work with automations is in blocking an automation when a condition isn’t met.
On Pro and Enterprise, the same data validation rules also check what an app writes through monday.com’s API, so a form app that writes to your board meets them too.
Catch Bad Answers After They Arrive
On any plan, most bad answers can be stopped by how the form asks, and the rest caught before they cause harm. None of these stops a respondent from typing a wrong value; together they make wrong values rare and visible.
Offer choices instead of free text
Where an answer comes from a known list (countries, months, service types, sites), use a single or multi select. People can’t type a wrong value when they pick from a list. For dates people find hard to type, a Date question is better than a text one.
Show the format in the question
Each question has a description under it. Use it to show the format, with an example: “Mobile number with area code, such as 416 555 0199.” It doesn’t stop errors, but it is the cheapest way to cut them, and it is the one place a respondent reads at the moment they type.
Set the Phone question’s country prefix
If most people answer from one country, set it as the default, so nobody leaves the country code off.
Review new items before automations use them
Give the board a status column such as “Review” with Waiting and Checked, set to Waiting on every new item from the form. Point the automations that send emails, texts or invoices at Checked, not at item created, so they run only after someone has looked. The ways to hold an automation until a column is right, from the workflow builder’s conditions to required columns, are in stopping an automation when a column is empty.
Send a confirmation email to the address given
An automation that emails the respondent on submission is the only native check that an address works: when it bounces, the address was wrong. Name the address in the email’s first line, so people who don’t receive it know to check what they typed.
A Line to Put in the Question’s Description
For the fields a form can’t check, one line in the description does most of the work. For example, under a vendor’s tax number:
Your GST/HST number: 9 digits, then RT and 4 digits, such as 123456789RT0001. We check it before we pay the first invoice.
Change the example to your own field. A line that says why the answer matters, and when it will be checked, gets more careful answers than one that only gives the format.
When You Need Pattern Checks: a Form App
When a code, ID or phone number must match a pattern before the form can be sent, monday.com’s own form can’t do it on any plan, and a form app from another company can. Two that connect to monday.com describe their checks on their own pages. They are other companies’ products; we describe them from their pages as read on Nov 15, 2026, and we have not tested them.
| App | What it checks before people submit | Plan | Writes to monday.com |
|---|---|---|---|
| Fillout | Min and max length, a regex pattern or a condition, with your own error message; whether an email address really exists (a paid add-on) | Field validation on every plan, Free included | Creates items, or updates an existing item through a link per item |
| Jotform | A validation option per field, a character limit and an input mask; an email confirmed before submit (a widget) | Its free Starter plan lists all features | Connects to monday.com |
Fillout puts validation in each field’s settings: a minimum and maximum length for text fields, an error message of your own, and a validation pattern, either Regex or Condition. Its help gives examples such as ^\d+$ for whole numbers. Its pricing page lists “Field validation” on every plan, Free included. Checking that an email address really exists is different: Fillout calls an outside service, and it is part of its Conversion Kit, “a paid add-on that an admin can add on any Fillout plan, including Free” (Fillout help, Fillout email validation, Fillout pricing). Fillout connects to monday.com with your monday.com API key and one board per form, and can also update an existing item (Fillout help).
Jotform’s Short Text field has a Validation option for the type of input allowed, a Character Limit with a minimum and maximum, and an Input Mask that fixes the format as people type: @ for a letter, # for a number (Jotform help, updated Sep 17, 2026; input masking). Its E-mail Validator widget makes respondents confirm their address before they can submit (Jotform help). Its pricing page lists the free Starter plan with “All Features Included”, five forms and 100 submissions a month (Jotform pricing).
What each app costs as you grow, and how each connects to monday.com, is in our comparison of monday.com form apps. If the form must change an item that already exists rather than make a new one, the ways to do that are in updating existing items from a form. BoardBridge, our own forms app, doesn’t have validation rules in its published feature list.
Example: A Vendor Intake Form
This is our own illustration, not a client’s form. Say a production company sends an intake form to new vendors with six questions. Here is what each way can check:
| Question | Standard | Pro and Enterprise | Fillout |
|---|---|---|---|
| Company name | Required | Required | Required, at least 2 characters |
| Contact email | Required; no format check documented | Required; no format check documented | Required; the address really exists (paid add-on) |
| Mobile number | Required; country prefix | Required; country prefix | Required; a phone pattern |
| GST/HST number | Required; any text | Required; any text | Required; the pattern 9 digits, RT, 4 digits |
| Available from | Required | Required; from a set date, moved by hand | Required |
| Quote amount | Required | Required; over 0 | Required; a condition, over 0 |
On Standard, the form makes sure nothing is blank, and the rest is the description line and a review. On Pro and Enterprise, two of the six get a real rule. Only a form app checks the email, the phone number and the tax number before the form is sent. For the GST/HST number, the regex ^\d{9}RT\d{4}$ matches the format, 9 digits, RT and 4 digits; whether the number is real, no pattern can tell.
We set up monday.com forms for clients. Why this guide is still fair:
- It starts with what monday.com’s own form checks, on every plan, before any app.
- Every monday.com fact links monday.com’s article, with the day we read it.
- Where monday.com’s articles are silent (what a respondent sees, a format check on email), we say so and give a test.
- Fillout and Jotform are described from their own pages, as not tested by us, and we sell neither.
Test the Form Before It Goes Out
A form with rules has more ways to go wrong than one without, so test it the way people will answer it:
- Break every rule once. Give each question with a rule an answer that should fail, and one that should pass, so you know what a respondent sees.
- Try the fields with no rule. Type “abc” in the Email question and a short number in the Phone question, and see what lands on the board. Change the description lines to match.
- Send one real answer. Point the form’s answers at a group called Test, as in step 8 of creating a form, and check every answer reached its column.
- Check the automations once. A submission starts the board’s automations like any other, so check that the review status held them, then delete the test item and point the answers back to their real group.
Have Clean Form Data Set Up
What we set up when bad form answers break your work:
- Questions that ask well: choices for every answer that comes from a list, the format shown in each question, the Phone country prefix.
- Required questions and, on Pro and Enterprise, the data validation rules and required columns your board needs.
- A review status on the board, and automations that wait for it before they send emails, texts or invoices.
- A form app with pattern checks, such as Fillout or Jotform, connected to your board, when codes and IDs must match before people submit.
- Custom forms and apps on monday.com when the checks go past what WorkForms and the apps can do.
Vendor, client and job intake forms are where bad data costs the most, because their answers feed emails, routing and invoices. We have done 85+ full implementations of monday.com for 110+ clients and built 25+ custom monday.com apps, and we tell you whether the native checks are enough before you add an app.
We’re based in Canada · Working with clients across North America and Europe
Show us the form that lets bad data in
Book a free call with a certified monday.com partner. We’ll say which checks fit each field, and set them up or build the form for you, with a fixed quote if you want us to.
- Certified monday.com Partner
- Free 30-minute call
- Reply within 2 business days
- We sign an NDA
What to Choose
Make the questions that matter required, offer choices instead of free text, and on Pro or Enterprise add number and date rules. For email, phone and code formats, review answers as they arrive or use a form app.
Put shortly: a form whose answers come from lists needs only choices and required questions; a form with amounts and dates needs data validations on Pro or Enterprise; a form whose emails and phone numbers feed automations needs a review step before they run; and a form whose codes must match a pattern needs a form app.
Frequently Asked Questions
Can a monday.com form check that an email address is valid?
Not that monday.com documents. An Email question fills an Email column, and monday.com’s articles describe no format check for it, so test what your form accepts. On any plan, an automated confirmation email to the address given flags a bad one when it bounces. Fillout can check that an address really exists, as a paid add-on.
How do I make a monday.com form check a phone number’s format?
monday.com has no phone format rule on any plan. The Phone question can set a default country prefix, and its description can show the format with an example. To stop a badly formed number before the form is sent, use a form app: Jotform’s input mask or a regex pattern in Fillout.
Does monday.com WorkForms support regex validation?
No. A WorkForm checks that required questions are answered, and on Pro and Enterprise the board’s data validations add limits such as numbers and dates, not patterns. For a code or ID that must match a pattern, Fillout lists regex in field validation on its free plan, from its own pages.
Do monday.com data validations work on forms?
Yes, on Pro and Enterprise, as long as the rule’s column is in the form. The rules can require a number over a set amount or a date from a set date. They can’t use dates relative to today, and a conditional rule doesn’t work when its “if” question appears but its “then” question is hidden.
Can a monday.com form only accept future dates?
Not as “after today”. On Pro and Enterprise, a data validation rule on the Date column can accept only dates from a set date, which you move by hand. Rules relative to today aren’t supported, so on any plan show the expected date in the question and review dates as they arrive.
We’re based in Canada · Working with clients across North America and Europe
Still have a question?
Ask a certified monday.com partner on a free call: the form, the fields that let bad data in and the automations behind it.
- Certified monday.com Partner
- Free 30-minute call
- Reply within 2 business days
- We sign an NDA
How We Reviewed This Guide
We wrote this guide from monday.com’s own pages. Its Help Center articles “Data validations”, “Required columns” and “WorkForms question types” were read between Oct 27 and 29, 2026; on Nov 15, 2026 the Help Center answered with a bot check, so we did not read them again by any route, and we give the date we read them. Fillout’s help articles on form validation, email validation and its monday.com integration, its pricing page, and Jotform’s help articles on the Short Text field, input masking and email verification and its pricing page were read on Nov 15, 2026. Typeform’s help answered with a bot check, so it is not on this page.
We did not take screenshots or test these rules in a monday.com account: where monday.com’s articles are silent (what a respondent sees when a rule stops them, whether an Email question checks the format), we say so and tell you what to test. The vendor form is our own illustration, not a client’s form. We have not tested Fillout or Jotform. BoardBridge is our own app, and we say so wherever it appears. If monday.com changes what its forms check, tell us and we will check it and update the guide.





