Log survey feedback on your product board
Survey responses land on your product board as tagged items you can group by theme during planning.
New submission on your feedback survey
Create an item on your Feedback board with the comment in a Long Text column, a category dropdown, and the submitter's email
One-directional. A submission triggers the action — nothing is written back into your form.
Qualitative feedback is only worth collecting if the team can find it again. Sending each response to a monday.com board turns loose comments into rows that can be sorted, tagged and pulled up in a planning session months after somebody wrote them.
Product managers running a rolling survey lean on this hardest. The board becomes the record, so a sprint conversation starts from what people actually wrote rather than what someone remembers hearing in a call.
Setting it up
- 1
Publish your survey from the Product Feedback Survey template, so each response arrives carrying a product name rather than as unattributed free text.
- 2
On the Feedback board, add a Long Text column for the comment and a dropdown column for the product or theme.
- 3
In Zapier, set the formformform "New Submission" trigger to the survey and add the monday.com "Create Item" step on the Feedback board.
- 4
Map "What features are missing or need improvement?" into the Long Text column — that is the answer the team will actually read in planning.
- 5
Map Product Name or Model into the dropdown, so the board can be grouped by product when the roadmap conversation starts.
- 6
Map Email Address to an Email column, so a PM can follow up on a comment worth a conversation without searching the responses list.
- 7
Use Your Name as the item name, or build the name from the product and the date if you would rather the board read by theme than by person.
- 8
Send a test response with a long answer, confirm it arrives whole rather than truncated, then turn the Zap on.
What maps where
Using the Product Feedback Survey as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | monday.com |
|---|---|
| Your Name | Item name on the Feedback board |
| What features are missing or need improvement? | Long Text column with the comment |
| Product Name or Model | Product dropdown column |
| Email Address | Email column for follow-up |
| Would you recommend this product to a friend or colleague? | Sentiment status column |
| How long have you been using this product? | Tenure dropdown column |
Variations worth knowing
The answer to "What features or aspects do you like most?" and the improvement answer can go to different groups, or different boards. Marketing works the first for testimonials, the roadmap takes the second.
A Zapier filter on the recommendation answer pushes detractors into a group a PM reads daily, while everything else accumulates quietly for the monthly read-through of the board.
If something isn't arriving
The item name is probably set to a static value, or mapped to a field most people leave blank. Point it at Your Name, or join two fields in the Zapier step so each row can be told apart on a long board.
monday.com will keep creating labels while the column allows it, so "Very easy" and "very easy" become two entries. Turn off new-label creation on the column and match the survey's wording to the labels already there.
Frequently asked questions
Can anonymous feedback go to a board like this?
It can, provided the survey does not ask for a name or an email and neither is mapped. Only the fields you map reach monday.com, so an anonymous survey stays anonymous once it is on the board.
Can one response go to the board and somewhere else too?
Yes. A single Zap can hold several action steps, so the same submission can create the monday.com item and post to a channel or a sheet. All of them read the same trigger, and none of them write back to the form.
Does the whole survey end up on the board?
Only the fields you map. A twelve-question survey can arrive as three columns, with the rest kept in your formformform responses list. Most teams map the comment, the category and the email, then export the remainder when they need it.
Related automations
- Add new sales leads to your pipeline board
Each sales enquiry lands in the New leads group of your CRM board, tagged "New lead" and ready to work.
- Build a guest list from every event RSVP
RSVPs build your attendee board as they arrive, keeping headcount and ticket mix current without manual entry.
- Drop new applications into the Applied group
Each application becomes an item in the Applied group of your recruiting board, tagged with the role applied for.
- Log problem reports as tickets on a triage board
Reported problems open as items on your support board, carrying the description and the priority the reporter chose.
- Track custom order requests on a fulfilment board
Custom order requests arrive as To do items on your orders board, with quantity in a numbers column.
- Add every RSVP to your confirmed guest list
Each RSVP creates a card on the "Confirmed guests" list with the ticket type as a label and dietary notes in the description.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free