Build a form with choices from your database

1. Add a Database choice question and pick the app, then the database, table or tab.
2. Choose the title and up to three details shown under each option, and add rules like Status is Open.
3. Share the form. New and changed rows appear within a few minutes, without publishing again.

Only the rows you mean to offer

Rules decide which rows are offered: Status is Open, Date is on or after today, Seats left is more than 0. Close a workshop in your database and it’s gone from the form. Sort the list by any field, and show up to three details under each option, like a date, a place or a price.

Respondents see only the title and those details; the rest of your rows never leave Nextforms. A list holds up to 2,000 rows, and if the app can’t be reached, the last list keeps working for up to a day.

Picked like any other choice

Show the options as a searchable dropdown, a list or buttons, the same as a Multiple choice question. Allow one answer or several, with a limit if you want one. A link can prefill a pick by its title.

Linked back where it came from

In Notion, the pick can be written as a relation: the new page links to the rows that were picked, so a rollup on your events database counts the sign-ups per event without anyone copying names around. Airtable works the same way with a Link to another record field: the new record links to the records that were picked, in the same base. Everywhere else, the picked titles are written, in Sheets, emails and Slack alike.

Conditions, piping, the responses table and exports all treat the pick by its row, so renaming a row later doesn’t break a rule.

Good for

• Event and class sign-ups: only sessions with seats left.
• Order forms: the products in stock, with their price as a detail.
• Bookings: rooms, equipment or time slots from your own list.
• Requests: pick the client or project from the database you already keep.

See Database choice for the setup, step by step.