Let users leave feedback from the screen they're on, and give your team a Notion database to triage it. You end with a native form in your product that adds every accepted response to Notion.
Build the form
Start from the shadcn form guide or the Next.js feedback card. Ask what the user was trying to do, then offer an optional reply email. Don't require contact details to report a rough edge.
Keep the field IDs stable, for example message and email. If you need trusted account context, sign respondent identity on your server. A hidden browser field doesn't prove who submitted.
Connect Notion
- Publish the form and collect one test response in Fillo.
- Open Settings > Connections and connect Notion.
- Share a parent page with the integration during authorization.
- Open the form's Settings > Response destinations and enable Notion.
- Choose the feedback message as the Notion title field.
- Submit a new test message and find it in the database Fillo created.
The Fillo connection in Notion's gallery is live. Install through Fillo's connection flow so the workspace and the form destination are set up together.
Add a triage view
Fillo writes the submission date, response ID, event type, and one property per form field. Add your own properties on top:
| Property | Type | Use |
|---|---|---|
| Triage status | Select | Empty until someone reviews the item |
| Owner | Person | Who follows up |
| Product area | Select | Where the feedback belongs |
Build an Unreviewed view that filters for an empty Triage status, then a board grouped by status. Keep the Fillo Response ID visible. It links a Notion item back to the stored response. Don't repurpose the properties Fillo maps to form fields.
Know how delivery behaves
Notion delivery is append-only and at least once. An edited response adds a new page marked Updated, so group by Fillo Response ID to keep related pages together. A rare retry can also add a duplicate page, so don't send money, grant access, or contact someone just because a page appeared. The Notion reference lists the field mapping and text limits.
Test the failure path
- Remove Notion access from a test destination.
- Submit a message and confirm the response is still saved in Fillo.
- Restore access and open delivery health.
- Replay the failed delivery and find the page in Notion.
Repair a failed delivery with replay. Don't ask the respondent to submit again. Keep private feedback and emails out of public screenshots.
Related
- Custom layout example: See native fields inside a product-owned layout.
- Notion integration: Check the field mapping, limits, and project settings.
- Build a shadcn form that saves responses: Use your existing inputs for the feedback form.
- Delivery health and replay: Find and repair a failed destination.