Automated restaurant call handling & table booking system with VAPI and PostgreSQL
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 workflow has 6 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Postgres.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Upsert Booking in Postgres (Postgres): create or update
- Query Table Availability (Postgres) (Postgres): select
- Respond: Booking Confirmation (VAPI) (Respond to Webhook): sends the response back to the webhook caller
- Respond: Availability Status (VAPI) (Respond to Webhook): sends the response back to the webhook caller
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 (3)
- Postgres
n8n-nodes-base.postgres - Respond to Webhook
n8n-nodes-base.respondToWebhook - Webhook
n8n-nodes-base.webhook
From the author
Acts as a virtual receptionist for the restaurant, handling incoming calls via VAPI without human intervention. It collects user details (name, booking time, number of people) for table bookings, checks availability in a PostgreSQL database using n8n, books…