User docs Collecting data

Forms and submissions

3 articles Updated 23/10/2026 01:50

Building a form, collecting submissions, and getting notified about them.

Forms are content, not code. You define one in the admin, place it on a page, and the submissions collect in one place regardless of how many pages it appears on.

The rule worth internalising

Every required field costs you completed submissions. Ask for what you need in order to respond, not everything you would eventually like to know. The single most effective improvement to almost any form is removing fields from it.

Handling what comes back

Submissions usually contain personal data, which brings real obligations: collect only what you need, agree a retention period and actually delete old entries, and be able to find one person's data if they ask. The best protection against mishandling a field is not having collected it.

In this topic

In this chapter

In reading order.

Building a form Define the fields, decide what is required, and place the form on a page. Read more Reading and exporting submissions Where submitted data goes, how to work through it, and what to keep in mind about personal information. Read more Notifications and follow-up Telling your team a submission arrived, and telling the person who submitted it that you received it. Read more

Objects ReferenceGenerated from the platform, so it is always current

API ReferenceEvery REST endpoint, in cURL, PHP, Python and JavaScript

Forms and submissions

The rule worth internalising

Handling what comes back

In this chapter