Professional Services and Consulting

<aside> 💼

Need help deploying, securing, or customizing this workflow? Contact [email protected] or visit paoloronco.it.

</aside>

Workflow resources

Overview

This workflow receives orders from an intranet menu, validates and normalizes their contents, records order history in n8n DataTables, and dispatches independent ntfy push and Italian Home Assistant TTS announcements through a local queue. It also provides indicative customer alcohol tracking, Telegram/email error alerts, a daily report, and configurable retention.

<aside> ⚠️

Deployment status: v4.2 hardened staging, not production-certified. Verify concurrent deduplication, receiver-side TTS idempotency, failure recovery and destructive maintenance before enabling it. The repository link above may still reference an older release.

</aside>

How it works

  1. Receive & validate: authenticated POST /menu accepts a stable UUID v4 orderId, customer identification, and non-empty order items; invalid requests return HTTP 400.
  2. Check order claims: the workflow consults the Notification SID Claims DataTable, returning 202 for an accepted order, 200 for a recognized duplicate, or 503 when claim storage cannot be trusted. DataTable lookups alone are not a transactional uniqueness guarantee.
  3. Save history: stores order_id, customer_id, customer name, formatted items, items_json, alcohol grams, date, and time in menu paoloronco intranet.
  4. Dispatch independently: sends an ntfy message with customer context and submits Italian speech to a local authenticated POST /announce queue. The queue implementation is deployed separately from the workflow.
  5. Track delivery: consolidates history, ntfy and TTS outcomes into completed, history_failed, ntfy_failed, tts_uncertain, or needs_review. Uncertain TTS delivery must not be replayed blindly.
  6. Alert on errors: Telegram and SMTP fallbacks carry order identifiers, affected services, and diagnostic details.
  7. Report daily: at 00:10 Europe/Rome, aggregates the previous day's orders, customers, products and indicative alcohol metrics.
  8. Maintain data: a planned Monday 04:00 retention process targets expired history and completed claims; automated destructive maintenance remains disabled until validated.

Before you begin