The Workflow That Sent the Right Message to the Wrong Person: Row-to-Recipient Mapping in n8n

说明与用途

在 n8n 工作流中，消息因行与收件人映射错误而被错误发送。通过使用业务键、唯一键检查、数据新鲜度规则以及发送步骤断言来防止此类错误。

问题

Messages were sent to incorrect recipients because row‑to‑recipient mapping failed silently.

结果

The workflow now prevents mis‑sent messages by enforcing key integrity, handling ambiguous lookups, and validating recipients at send time, reducing post‑send corrections.

工作流

• 1. Retrieve rows with business keys (lead id, customer id).
• 2. Enrich rows via lookups ensuring unique keys or fail on ambiguity.
• 3. Apply filtering/joins while preserving business keys.
• 4. Cache enrichment with freshness rules; re‑fetch or halt if stale.
• 5. In send node, resolve recipient from key independently and assert match with row’s key.
• 6. If assertion fails, halt run and create review item with both values.
• 7. If all assertions pass, send message to resolved recipient.

证据

The scariest workflow failure I have seen did not throw an error, did not page anyone, and did not show up in any success metric.

来源

The bug was never in the send step. It was in the mapping step, one or two nodes earlier, where a row and a recipient stopped belonging to each other.

来源

Before sending, assert that the recipient on the message matches the business key on the row, using an independent source.

来源