When creating a form, I would like to be able to create multiple subitem questions. The use case is that when a user selects an option from a multi-select box I would like to display certain text fields from the Subitem. When a user selects a different multi-select box I would like to display different text fields from the subitem. All responses can go into the same Subitem, but the user would only be shown the subitems questions that is tied to their response to multi-select box.
What are you trying to achieve
User experience: User is presented with Questions related to their answer to a multi select box.
Backend Experience: A new item is created on the board and all the answers are listed in the subitem.
In monday forms, subitems are the tricky part. Forms are great at creating a new item and using conditional logic to show or hide questions, but they do not natively support dynamically creating or filling subitems in the way you’re describing, and they do not let you conditionally show different “subitem question sets” that then land into subitems.
A few options people usually use instead:
Option 1 is to keep it all on the parent item
Use conditional form questions based on the multi select choice, and store the answers in regular item columns. This gives the clean user experience you want. If you still need subitems for internal workflow later, you can create them after submission using automations.
Option 2 is to use one form per scenario
If each multi select option represents a different “path,” some teams create separate forms for each path. Each form asks the relevant questions and maps them consistently. This is simple for users, but you end up with multiple forms to maintain.
Option 3 is to capture the data in the item, then create and populate subitems via integration
If you really need the answers to end up in a subitem row, the common approach is to submit the form to the parent item, then use an integration tool or custom workflow to create a subitem and move the captured fields into it. This keeps the form experience clean, and the backend ends up with subitems, but it’s not fully native.
If your priority is user experience, option 1 is usually the cleanest. If your priority is having everything stored in subitems immediately, option 3 is the closest match, but it requires an extra layer outside the form.
If you’d like hands-on help or want us to walk through this live, you can book a 1:1 paid 60-minute strategy session with our team here: Calendly
