Your users should be able to leave feedback from the screen they're using. Your team should be able to read and triage it in Notion. Fillo connects those two workflows: a native form in your product, with accepted responses delivered into a Notion database.
Start with one useful question
Use the shadcn feedback example or Next.js settings-page starter. Ask what the user was trying to do, then offer an optional reply email. Don't require contact details just to report a rough edge.
Keep the field IDs stable. For example, use message for the feedback and email for the optional reply address. If you need trusted account context, generate respondent identity on your server; a hidden browser field is not proof of who submitted.
Connect the inbox
- Publish the form and collect one authorized 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. Open the database Fillo created under the shared parent page and find that message.
The Fillo connection in Notion's gallery is live. Install through Fillo's connection flow so the workspace and form destination are configured together.
Give the team a triage view
Fillo writes the submission date, response ID, event type, and mapped form fields. In Notion, add team-owned properties such as Triage status, Owner, and Product area. Build an Unreviewed view where Triage status is empty, then a board grouped by that status.
Keep the response ID visible. It connects the Notion item back to the stored response when someone needs to inspect delivery, export answers, or investigate an edit. Use your own triage properties for decisions; avoid repurposing the properties Fillo maps to form fields.
Understand edits and retries
Delivery is append-only. A later edit to the same Fillo response creates another Notion page with Fillo Event = Updated; it doesn't edit the original page. Group by Fillo Response ID if you want related entries together. This recipe is an inbox, not a two-way issue tracker.
External delivery is at least once. A retry may happen after an ambiguous network failure, so don't build a workflow that sends money, provisions access, or repeatedly contacts someone just because a new Notion page appeared.
File answers are formatted into rich text; their bytes remain in the workspace's connected storage. They don't become native Notion attachments. The Notion reference lists the exact field mapping and text limits.
Verify the failure path
Before sharing the form widely, use a test destination to check what happens when Notion access is removed. The response should still be saved in Fillo. Restore access, inspect delivery health, replay the failed destination, and verify the Notion result. Don't ask the respondent to submit again to repair a delivery failure.
Put it in your product
Start with an agent to add the native feedback form, then connect Notion in the dashboard. Keep private feedback and emails out of public demo screenshots.
Related
- Support intake example: Try an intake flow before connecting a destination.
- Agent setup to first response: Verify the full publish and submit loop.