Your Workflow Said Success and Nothing Happened: Verifying Side Effects in n8n

Описание и применение

В n8n добавление шага проверки после внешних записей выявляет скрытые ошибки, превращая «успех» в подтверждённый результат и повышая надёжность процессов.

Задача

A workflow reported success after calling an external API, but the intended side effect (e.g., creating a CRM record) never occurred, leading to silent failures that went unnoticed for days.

Результат

Adding a read-back verification step after external writes turned silent failures into visible, actionable outcomes, reducing missed leads and improving reliability.

Рабочий процесс

• 1. Enrich new lead data
• 2. Call external API to create CRM record
• 3. Log node status as green
• 4. Add verification node: read back record by lead ID or email
• 5. Compare read-back with expected data
• 6. Classify outcome: verified, failed, or pending-review
• 7. Update run summary with verification results

Доказательства

The execution log was clean: every node green, final status success.

Источник

The verify step has three outcomes, and they map exactly to the buckets I use everywhere else: verified, failed, and pending-review.

Источник

Once you verify, the run summary stops lying in a useful way. Instead of "success: 50," you get "verified: 48, failed: 1, pending-review: 1."

Источник