2 Commits

Author	SHA1	Message	Date
mivanchenko	a27ee59125	Owner notification webhook: Telegram re-point (#23) ... Flask fires a fire-and-forget internal webhook (owner_notify.py, mirroring mailer.py's background-thread queue) on booking create/cancel/reschedule, carrying the same {booking, business_name, notify_channel} shape the old EA-driven "Build booking row" node produced, plus an event field so the Telegram message can say what actually happened. n8n/booking-sync.json gets a new webhook + IF node feeding the existing Telegram node directly, so it no longer needs EA's API to build the notification payload; channel routing (only telegram sends for now) lives in that IF node. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-04 12:09:39 +02:00
mivanchenko	156166b4e5	Add booking stack, client deploys, and back-office updates ... - deploy/booking: shared Easy!Appointments stack with brand-matched wizard (flatpickr recolor, single-tenant provider hide, iframe auto-fit height reporter) - deploy/clients: per-client isolated nginx compose stacks with _template scaffold, new-client.sh, and happynails live site - deploy/backup: smb-db backup script - n8n: booking-sync workflow; onboarding tweaks - playbooks: lead-to-customer lifecycle + outreach - templates: nail-studio landing previews - backoffice: app/db/init/compose updates Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-14 16:10:15 +02:00