Instance · Forms
Instance forms overview
Last updated 7 November 2026
Build forms without code: choose a database, lay out fields, set messages, security and emails.
The form builder lets you build forms without code. You choose the database that stores the answers, lay out its fields and set what happens on submit. Two emails go out: a reply to the person who filled it in and a notice to your team. Your site then shows the form from the embed code the builder generates.
The parts of a form
| Tab | What you set |
|---|---|
| Details | Name, the database answers go to, where to send people after submitting, and spam protection |
| Settings | What runs on submit, the success and error messages, and the button |
| Fields | Which fields show, their labels, placeholders, tooltips, validation, steps and conditional visibility |
| Form Code | The code to embed the form on a page |
| Security | The authorization policies a submission must pass |
| Email Notifications | One reply to the submitter and one notice to your team |
On a new form, choose the database first: the last four tabs stay disabled until you do. The builder uses the database's own fields; it does not create new ones.
Example: the forms on an instance
Query
{
admin_forms(per_page: 50) {
total_entries
results { name flash_notice }
}
}Response on the docs instance
{
"data": {
"admin_forms": {
"total_entries": 3,
"results": [
{ "name": "modules/ins_forms/documentation_suggest_changes", "flash_notice": "Successfully submitted form." },
{ "name": "modules/website/contact_us", "flash_notice": null },
{ "name": "modules/website/subscribe", "flash_notice": null }
]
}
}
}This ran read-only on the docs.insites.io instance on 1 November 2026.
Common mistakes
- Selecting Generate Form Code after editing the code by hand. It replaces your edits, after a confirmation.
- Building a form before the database has the fields you need. Add the fields in Data first.
- Publishing a form with no spam protection or policy.