Weavely lets you set validation rules on every field where respondents can type freely. This ensures you only collect clean, correctly formatted data. No more garbage responses to clean up later. This guide covers validation options for each input type and shows you how to use custom patterns (with help from AI) for advanced rules.Documentation Index
Fetch the complete documentation index at: https://help.weavely.ai/llms.txt
Use this file to discover all available pages before exploring further.
Text inputs (short and long)

Example: require text to start with “hello”
Describe your rule to the AI
In the Weavely AI chat, type something like: “All of the inputs in the long text input question should start with hello in order to be valid.”
AI generates the regex pattern
Weavely’s AI creates a regular expression and automatically fills it into the custom pattern field for that question.
Number input

Example: require numbers starting with “91”
Describe your rule to the AI
In the AI chat, type something like: “A response is only valid if it starts with 91 and then anything after that.”
AI generates the pattern
The AI creates a regex and sets it in the pattern field for your number input.
Email input

@ symbol to be accepted. No configuration needed.
Custom pattern (regex)
You can add a pattern to further restrict which emails are accepted. For example, if you only want to allow Gmail addresses, describe that rule to the AI and it will generate the appropriate pattern.
Phone number input

+1, +44, +32), the form will reject it.
Custom pattern (regex)
You can further restrict phone inputs by specifying a pattern — for instance, only accepting numbers from a specific country code.
URL input

http:// or https:// followed by the rest of the address. Entering just a domain name like weavely.ai without the protocol will be rejected.
Min / max length and custom pattern
You can also set length restrictions and custom patterns on URL fields. For example, you could restrict inputs to only .com domains.
Date and time inputs

Quick reference
| Field type | Built-in validation | Configurable options |
|---|---|---|
| Short text | — | Min/max length, custom pattern |
| Long text | — | Min/max length, custom pattern |
| Number | — | Min/max value, custom pattern |
Must contain @ | Custom pattern | |
| Phone | Requires country code | Custom pattern |
| URL | Must start with http(s):// | Min/max length, custom pattern |
| Date | — | Min/max date |
| Time | — | Min/max time |
For any field that supports a custom pattern, you can always ask the AI to generate the regular expression for you. Just describe the rule you want in plain English, no regex knowledge required.