I Solved the Same Gmail Problem Two Ways Without Noticing

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

В рабочем процессе n8n Gmail‑узел заменяет исходные данные отправки подтверждением, из‑за чего последующие шаги теряют поля. Перестроив поток, автор восстановил данные после отправки и перенёс логирование в Google Sheets сразу после классификации, чтобы оно не зависело от успеха письма.

Задача

The Gmail node in the n8n workflow replaced the original submission data with its own send confirmation, causing downstream steps to lose necessary fields such as Name, Email, and description.

Результат

The workflow now logs every submission regardless of email success, eliminates duplicate logging, and corrects email routing errors.

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

• 1. Classify submission into one of five categories via Switch node.
• 2. For each category, send a category‑specific email using Gmail node.
• 3. Rebuild the original submission object with a Set node after the email step (except in ambiguous/system_error branch where a rebuild node precedes the email).
• 4. Log the submission to Google Sheets using a single shared Sheets node at the end of all branches.
• 5. Move the Sheets logging to two points right after classification: one for successful classification and one for failure handling, running in parallel with the Switch.
• 6. Verify email destinations by checking real inboxes and correct any swapped addresses.
• 7. Test classification with both vague and explicit descriptions to confirm classifier behavior.

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

When the Gmail node sends an email, the item it passes on is Gmail's own send confirmation, not the submission.

Источник

I moved the Sheets connection to the two points right after classification: one for a successful classification and one for the failure handler.

Источник

After the rewiring, I retested every branch individually and checked real inboxes, not just node output.

Источник