Error Handling and Edge Cases in the Restaurant Booking n8n Workflow

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

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

Задача

Missing or malformed data from a web form can cause null entries in Google Sheets or failed email confirmations, leading to unreliable restaurant bookings.

Результат

The workflow automates booking capture and confirmation but exposes failure modes such as null entries, duplicate rows, network errors, and email rate limits that need manual or additional error handling.

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

• Form Trigger – formTrigger: receives JSON payload from web form
• Set – Preprocess Form: maps form fields to Google Sheet columns
• Google Sheets – Insert Booking: writes booking row into spreadsheet
• Email – Send Confirmation: sends confirmation email via Gmail

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

Form submissions missing required fields pass empty values downstream, potentially causing null entries in Google Sheets or blank email recipients, requiring form-side retries to guarantee complete data.

Источник

The Set node maps form fields to sheet columns; mismatched labels or quick resubmissions can result in empty columns or duplicate rows unless external duplicate checks are implemented.

Источник

Google Sheets writes booking data but fails silently on network errors or row limits without automatic retries, and Gmail confirmation sends fail on malformed addresses or API rate limits, logging errors and moving on without retrying.

Источник