從意見回饋表單到團隊收件匣：建立可追蹤的工作流程
From Feedback Form to Team Inbox: A Traceable Workflow
可追蹤的意見回饋自動化流程，應由來源訊息連結至明確的處理行動，並保留穩定識別碼、處理狀態和時間戳記。BMRC Hospital 項目帳戶記錄了一套使用 n8n、OpenAI、Supabase 和 Gmail 的多語言意見回饋分流流程。設計建議亦涵蓋通知驗證、例外處理及失敗後的復原規則。
Introduction
Feedback automation is most useful when it connects the original message to a clear next action. A label alone does not tell a team where to respond, who owns the case, or whether the notification was delivered.
My published BMRC Hospital project account describes an n8n, OpenAI, Supabase, and Gmail workflow for multilingual feedback routing. The design suggestions here are a general planning pattern, not a claim that every detail is part of that implementation.
Give each item a stable identity
Assign or preserve an identifier as early as possible. If the source sends the same event again, the workflow can check whether it has already been processed rather than creating duplicate records or notifications. Store the identifier with processing status and relevant timestamps.
Store the decision and make notification verifiable
Keep the original message or a protected reference, the generated category, the applied routing rule, and the final destination together. Where practical, record which model or workflow version produced the suggestion. Avoid storing unnecessary copies of sensitive content; access and retention should follow the organization's policy.
Creating a ticket and notifying its owner are different actions. Capture whether the notification service accepted the request, and define what happens if it fails. The case should remain visible in the system of record even if email is temporarily unavailable. A retry should not create another ticket or repeated alerts without an explicit reason.
Plan exception paths
Test missing message text, unsupported language, ambiguous category, duplicate event, database error, and email failure. For each case, specify whether to retry, pause for a person, or mark the item for follow-up. Alerts should identify the workflow and record without exposing more customer information than necessary.
Stable identifiers, separate processing states, and explicit recovery rules help a team trace the path from source message to final owner. See the BMRC feedback-routing case study for the documented project scope.
Originally published at Kriyvo AI: https://kriyvoai.online/blog/feedback-form-to-team-inbox-workflow
來源：DEV Community · dev.to