Aamu.app Forms let you build survey forms, feedback forms, sign-up forms, internal request forms, and small data-collection workflows without wiring together a separate form tool and a separate spreadsheet. The form is public when you publish it, and the responses are stored in an Aamu database table.

That database connection is the important part. A form is not just a page that sends you an email. Each submission becomes structured data that you can review, filter, export through your workflow, automate, or use from the Aamu API.

Create a new form

Open the Forms section in the project where the survey should live, then create a new form. Forms are project-scoped, so choose the project deliberately: the project controls where the form appears, which team members work with it, and where the connected response database belongs.

A new form starts as a draft. Give it a clear title and, if useful, a short description that tells respondents what the form is for. For a survey, this is usually enough:

  • what you are asking about,

  • how long it will take, and

  • what happens after the respondent submits it.

Add survey fields

Use Add new field to build the form. The current field types cover the common survey cases:

  • Text answer for short free-text answers,

  • Paragraph for longer open answers,

  • Choice for radio buttons, dropdowns, or checkboxes,

  • Date/time for dates, times, or date-time values, and

  • File upload for attaching files to the response.

Each field can have a title, description, placeholder text where relevant, and a required toggle. Choice fields can be one-choice radio buttons, one-choice dropdowns, or multiple-choice checkboxes.

For surveys, avoid making every field required. Required fields are useful for must-have data such as email address or consent, but too many required fields make people abandon the form.

Think in database columns

When you publish a form, Aamu connects the form to a database table. The form fields become structured columns, and each submission creates a row.

This has two practical consequences:

  • After a field has been published into the database, its type is part of the response structure.

  • If you change a published form, publish the new elements so the database table and public form stay in sync.

This is why the editor distinguishes draft changes from published form structure. You can keep editing, but the public form and the response database need an explicit publish step when the structure changes.

Configure form settings

Open the form Settings tab before publishing. The useful settings are:

  • Short url for a cleaner public link,

  • Thank-you page for redirecting successful submissions,

  • Error page for redirecting failed submissions,

  • Submit button text for matching the form's purpose, and

  • Custom CSS for adjusting the public form's appearance.

If you do not set custom thank-you or error pages, Aamu uses default pages. For public surveys, a custom thank-you page is often worth adding because it can tell the respondent what happens next.

Publish and share the form

Publish the form when it is ready. After publishing, Aamu shows a View form link. The public URL uses this shape:

https://YOUR_AAMU_SUBDOMAIN.aamu.app/shared/form/FORM_ID_OR_SHORT_URL

Use the generated link from Aamu. If you configured a short url, the public link can use that instead of the raw form id.

Before sending the link to real respondents, submit the form once yourself. Check the thank-you page, required fields, choice labels, file upload fields if any, and the resulting response row.

Review responses

Once the form is public, the form header includes a Responses tab. Aamu shows both a summary view and the underlying database connection.

The summary view is useful for quick survey reading: choice fields can be charted, and text fields can be reviewed as collected answers. The details view shows the actual database rows. Aamu also links directly to the database table, where you can work with the responses like any other database data.

This is helpful when a survey turns into work. For example:

  • a feedback form can create follow-up tasks,

  • a sign-up form can become a customer or lead list,

  • a bug-report form can be triaged in a database view, and

  • a file-upload form can keep attachments connected to the response row.

Automate after responses arrive

Because responses are stored in a database table, you can use database automations for follow-up work. For example, a response can lead to a task, a notification, a status change, or another internal workflow.

The form itself collects the data. The database and automations are where the response becomes part of the team's work.

Using the Forms API

For normal public surveys, use the published form link. A browser visitor does not need an API key to submit the public form.

For integrations, Aamu also has an authenticated Forms API. API keys can list forms, fetch a form definition, and submit form responses with Forms scope:

GET  /api/v1/forms/
GET  /api/v1/forms/{id}
POST /api/v1/forms/{id}/submissions

Use the API when another system needs to submit structured responses into Aamu. Use the public form when a person is filling in a survey in the browser.

A simple survey checklist

  1. Create the form in the right project.

  2. Add a short title and description.

  3. Add fields with clear labels.

  4. Mark only the necessary fields as required.

  5. Configure the short url and thank-you page.

  6. Publish the form.

  7. Open the public link and submit a test response.

  8. Check the Responses tab and the database row.

  9. Add automations if responses should trigger follow-up work.

That is the main advantage of building surveys inside Aamu.app: the form, the response data, and the follow-up work can live in the same project instead of being split across a form builder, a spreadsheet, and a task tool.