File survey feedback in your Notion research database
Each survey response becomes a tagged entry in your Notion research database, ready to group by theme during planning.
New submission on your feedback survey
Create a page in your Feedback database with the comment, a category select, and the submitter's email
One-directional. A submission triggers the action — nothing is written back into your form.
Qualitative feedback is easy to collect and easy to lose. This flow files each survey response as a page in the Notion database the product team already reads from, with the verbatim comment in the body and the product it concerns set as a select.
Teams reach for it before a planning cycle. Grouping the database by category turns a month of scattered replies into a handful of themes, and the score sits on each page as a number, so a low rating and the reason for it stay attached to one another.
Setting it up
- 1
Publish the survey with your product lines as the answers to "Which of our products or services did you use?" That question becomes the category select in Notion.
- 2
In Notion, set up the Feedback database with a title, an Email property, a Number property for the score, and a Category select whose options match those answers exactly.
- 3
In Zapier, select formformform and the New Submission trigger, choose the survey, and pull a sample response through so every answer is available to map.
- 4
Add the Notion "Create Database Item" action and point it at the Feedback database.
- 5
Build the page title from two tokens, the respondent's name and the product they named, so the board is readable without opening anything.
- 6
Map the 0 to 10 score into the Number property rather than a text one, so a view can filter down to detractors later.
- 7
Send the reason for the score to the page body, and add the improvement answer underneath it in the same content block.
- 8
Turn the Zap on, then group the Feedback database by Category so new responses appear under the right heading.
What maps where
Using the Net Promoter Score Survey as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Notion |
|---|---|
| Your Name | Part of the page title, alongside the product named |
| Email Address | Email property, so a researcher can arrange a follow-up call |
| On a scale of 0–10, how likely are you to recommend us to a friend or colleague? | Score number property |
| What's the main reason for your score? | Page body of the feedback entry |
| Which of our products or services did you use? | Category select |
Variations worth knowing
Add a Zapier filter that continues only when the score is six or below, and point that path at a second Notion database the customer team reviews weekly. Everything else still lands in the research log without crowding the follow-up list.
The survey asks respondents to name a specific product where the category answer is too broad. Map that answer to a text property and the database reads both ways: grouped by category for planning, searchable by product name when one launch is under review.
If something isn't arriving
The Notion property must be Number, and the Zap has to pass a bare figure. Where the answer arrives with words attached, trim it with a Zapier Formatter step before mapping, otherwise Notion stores nothing in that property at all.
The product question is optional in this template, so a respondent can skip it. Set a fallback value such as Unspecified in the Zap's Category field, and read that group once a week rather than losing the comment in an unfiltered list.
Frequently asked questions
How do we stop the research database filling up with one-word answers?
Make the reason question required in the form editor and the survey will not submit without it. A Zapier filter can also skip anything under a set length, so the shortest replies stay in the responses view instead of the Notion database.
Can a researcher reply to a respondent from the Notion page?
Not through the connection, which runs one way and writes nothing back to the survey. Mapping Email Address to a property gives whoever picks the entry up an address to write to from their own inbox, with the comment on screen beside it.
Should each survey have its own Notion database?
One database with a Source select is usually easier to live with. Themes cut across surveys, and a single database can be grouped, filtered and searched in one place. Split it only when two teams genuinely never read each other's responses.
Related automations
- Add every inbound enquiry to your Notion leads database
Every business enquiry lands in your Notion Leads database as a page tagged New, with the company and inquiry type already filled in.
- Build your Notion guest list from event RSVPs
Every registration adds a guest to your Notion attendees database, with ticket type, party size and dietary notes attached.
- Log new applicants in your Notion hiring pipeline
Each application arrives in your Notion candidates database as an Applied card, with the role and available start date already on it.
- Queue new orders in your Notion operations database
Each order request opens as a To do card in your Notion Orders database, with the product and quantity ready to pick.
- Turn problem reports into open tickets in Notion
Each problem report opens as a ticket in your Notion support board, already carrying a priority and the steps to reproduce.
- Add job applicants to a hiring pipeline
Each application becomes a Candidates record with role, start date and stage, ready to drag through a kanban view.
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