Slack Notification + Google Sheets Log

Goal: Prevent missed responses by notifying Slack and logging the same response to Google Sheets. Fields: Respondent email address, Response body, and Target date and time. Extract the name, request details, and any risk notes from the response body. Rules: At chat execution, review unlogged responses so the same response can be traced in Slack and Google Sheets. Actions: When this prompt is run in chat, review unlogged responses. Use the response ID as a deduplication key, post a 3-line summary through the connected Slack MCP, and append received time, email, summary, next action, and handling state through Google Sheets MCP. Check existing rows and posts first and record each write result separately. 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 Slack / Google Sheets 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.