Manage catering event quotes and countdowns with Postgres, Gmail, OpenAI and Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 63 nodes and runs when an HTTP POST request hits its webhook URL (plus 4 other triggers). Along the way it connects Telegram, Gmail, OpenAI Chat Model and Postgres.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 4 other triggers).
- Normalize Intake (Edit Fields (Set)): sets 14 fields: client_name, client_email, event_type…
- Normalize Update (Edit Fields (Set)): sets 4 fields: event_id, field, value…
- Fetch Open Events (Postgres): run a query
- Normalize Done (Edit Fields (Set)): sets 3 fields: event_id, final_headcount, _valid
- Validate Intake (If): checks a condition and branches into true / false
- Validate Update (If): checks a condition and branches into true / false
- Parse Open Events (Code): runs custom JavaScript code
- Validate Done (If): checks a condition and branches into true / false
- Build Quote Context (Code): runs custom JavaScript code
- Build Invalid Intake Notice (Edit Fields (Set)): sets 3 fields: tg_text, esubj, ebody
…plus 46 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Gmail
n8n-nodes-base.gmail - Code
n8n-nodes-base.code - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Postgres
n8n-nodes-base.postgres - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Catering quotes, invoices, and reminders that run themselves. This workflow takes catering inquiries through webhooks, has OpenAI (gpt-5.6-terra) draft the quote and invoice emails, stores every event in Postgres, and keeps clients and the owner in the loop…