Docs / Guides
Fields and limits
Any field with a name is stored. Fields that start with an underscore control how the submission is handled.
<form action="https://wrenform.com/f/YOUR_FORM_ID" method="POST">
<input type="hidden" name="_subject" value="New enquiry from example.com">
<input type="text" name="name" required>
<input type="email" name="email" required>
<label><input type="checkbox" name="topics" value="sales"> Sales</label>
<label><input type="checkbox" name="topics" value="support"> Support</label>
<textarea name="message" required></textarea>
<input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off">
<button type="submit">Send</button>
</form>Data fields
- Every input with a
nameis stored and shown in your email, dashboard and webhooks. Inputs without aname, and disabled inputs, aren't sent by the browser. - Fields keep the order in which they were sent.
- Names and values are trimmed of surrounding spaces. Control characters are removed, except new lines and tabs.
- A submission needs at least one data field with a value. Otherwise you get
422 empty_submission.
Reserved fields
Fields whose names start with _, plus cf-turnstile-response, are controls, not data. We read them, then remove them from the stored submission. Any other field that starts with _ is dropped.
| Field | What it does |
|---|---|
_honey |
Honeypot. Hide it from people; bots fill it in. Any value marks the submission as spam. |
_gotcha |
Same as _honey. Accepted so forms moved from Formspree keep working. |
_t |
When the form was rendered, as a Unix time in milliseconds. A submission less than 3 seconds later is spam. Ignored if more than 60 seconds in the future or older than 24 hours. |
_te |
Milliseconds since the form was rendered, measured on the visitor's own clock. Under 3,000 is spam. Wins over _t, so a visitor with a wrong clock isn't misjudged. |
_redirect |
Where to send the visitor after a successful browser submission. Must be an absolute http(s) URL on one of the form's allowed origins (or, with none set, the site that posted). Otherwise it's ignored. |
_subject |
The subject line of the notification email. |
_replyto |
The reply-to address of the notification. Without it, the first valid field named email, e-mail, mail or your-email is used. |
cf-turnstile-response |
Cloudflare Turnstile token, added by the Turnstile widget. Only checked if you added your Turnstile keys to the form. |
Reply-to
Your notification email's reply-to is set, in this order, to:
_replyto, if it holds a valid address;- the first field named
email,e-mail,mailoryour-email(any case) that holds a valid address; - nothing.
So name your address field email, and pressing Reply in your mail app answers the visitor.
Subject
The notification's subject is _subject if the form sends one. Otherwise it's the Email subject from the form's settings, where {form} is the form's name and {field:name} is the value of a field. The default is New submission: {form}.
Lists and checkboxes
- A name sent more than once becomes a list, in order. Give checkboxes in a group the same
name, liketopicsabove. - Unchecked checkboxes aren't sent at all.
- Brackets aren't special:
topics[]is stored as a field namedtopics[]. Plaintopicsreads better in your email. <select multiple>works the same way as a checkbox group.
JSON bodies
Send a flat object. Values can be strings, numbers, booleans or arrays of strings. Numbers and booleans are stored as strings. A nested object gets 422 invalid_json.
{ "name": "Ada", "email": "ada@example.com", "topics": ["sales", "support"], "message": "Hello" }Files
File uploads aren't supported yet. In a multipart/form-data post, file parts are dropped and their field names are noted on the submission. The text fields still arrive.
Limits
| Limit | Over it |
|---|---|
| Request body: 64 KB | 413 payload_too_large |
| 100 fields per submission | 422 too_many_fields |
| Field names: 100 characters | 422 field_too_long |
| Values: 10,000 characters | 422 field_too_long |
Add maxlength to inputs to stop visitors before they hit a limit. Nothing is stored when a request is over a limit.
Test it
Press Send test submission on the form's Setup page, or send your own form. Open the submission in your dashboard and check that every field is there, in order, and that reply-to shows the visitor's address.
Common problems
- A field is missing. It has no
name, it's disabled, or its name starts with_. - Reply goes to you, not the visitor. The address field isn't named
email(or one of the names above), or the value isn't a valid address. - Only one checkbox value arrives. The checkboxes have different names. Give the group one name.