Response to Notion Database

Goal: Save form responses into a Notion database in a searchable structure. Fields: Respondent email address and Response body. Extract category, summary, priority, and next action. Rules: Treat likely duplicates as update candidates, and create a new Notion record for new responses. Actions: Use Notion MCP to verify the target database and existing records, then create or append email, summary, category, priority, current handling state, received date, and FORMLOVA link. Match response IDs to prevent duplicates and do not replace existing properties by inference. Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them. Records: update_response accepts only new / in_progress / resolved / spam for status. Use status="in_progress" for new open work; do not reopen existing resolved/spam responses, and use resolved only when the work is verified complete. Immediately before changing business tags or notes, read their current values with search_responses. Pass the deduplicated full set of existing plus added tags (at most 20 tags, 50 characters each), or the full existing notes with the addition appended. If current values cannot be read or limits would be exceeded, ask instead of overwriting. Keep schedules and drafts separate from verified sends, writes, and attendance. External connections: Separate Notion MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.